On 25/04/06, Bruno POMMEREL <[EMAIL PROTECTED]> wrote: > > Thank you for taking time to address this pb. Digging into the code, I > saw that the addEncodedArgument() method is called from > HTTPSamplerBase::parseArguments(String queryString). As far as I understood > the code, it seems like we'd rather invoke addArgument() if we don't want to > have the query string translated from the original request. Is that correct ? >
That seems to always encode the names and values; as they are already encoded, we want either to leave them as is, or decode them so that they re-encode correctly. The code currently uses URL.encode() to do the work. This treats "-", "_", ".", "*" and alphanumerics as safe. Everything else is encoded. However according to RFC3986 there are other characters that should not be encoded when handling the query section of a URL, in particular "?". The simplest solution is to leave the names and values as is, assuming that the browser has already encoded them correctly. This should work in all cases, but the names and values won't always be easy to read. If you want to give it a try, the new nightly 2-1.20060426 has got the fix in it - query parameters should now be stored as is. S. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
