Summary: | Use specified encoding for parameter values in HTTP GET | ||
---|---|---|---|
Product: | JMeter - Now in Github | Reporter: | Alf Hogemark <alf> |
Component: | HTTP | Assignee: | JMeter issues mailing list <issues> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | ||
Priority: | P2 | ||
Version: | 2.2 | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All | ||
Attachments: | Suggested patch for encoding HTTP GET urls |
Description
Alf Hogemark
2007-04-12 04:38:05 UTC
Created attachment 19935 [details]
Suggested patch for encoding HTTP GET urls
The suggested patch lets the HTTPSamplerBase construct the query string by
encoding parameter values according to the specified encoding.
This also means that the PostWriter can use this
getQueryString(contentEncoding) method, instead of having it's own version of
the method.
I have also added unit tests to TestHTTPSamplersAgainstHttpMirrorServer. If you
only apply the unit test, then the test from line 353 will fail.
I.e. where the values are set like this :
titleValue = "mytitle\uc385";
descriptionValue = "mydescription\uc385";
Because these values look different when url encoded in utf-8 and iso-8859-1.
This patch will also make it easier to add functionality to the HTTP Proxy
server.
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/1908 |