The original bug was reported against TC4 so I have ported the patch in order to close the bug report. TC4 does not include the uRLEncoding parameter on the connector so I have implemented the queryStringEncoding parameter as Remy previously suggested. To make TC5 consistent with TC4, I have added the queryStringEncoding parameter to TC5 and modified CoyoteAdapter to use this new parameter. All the patches can be found below. Please could someone (Remy?) commit them.
I coldn't find a good reason why the queryString would have a different encoding from the rest of the URL. That's why I didn't add the flag at that time, and used the configured URI encoding for everything.
As for TC 4.1, I think its core components (connectors, deployer, main pipeline) should be frozen for non critical fixes. If there's interest, the big patches from TC 5 (ex: deployer, Coyote, etc) could be ported to a new 4.2 branch. But this may well be a dead end and a waste of resources, given the already close similarities between 4.1 and 5. Glenn wanted to do that a while ago, but he was a bit alone at that time.
Remy
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
