You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jmeter-dev@jakarta.apache.org by bu...@apache.org on 2004/01/24 04:09:25 UTC

DO NOT REPLY [Bug 25753] - Charset encoding of form request parameter

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25753>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25753

Charset encoding of form request parameter

woolfel@yahoo.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
           Priority|Other                       |Low



------- Additional Comments From woolfel@yahoo.com  2004-01-24 03:09 -------
In order to use the default charset encoding of the page, JMeter would have to 
first make a request to the website and extract the encoding. Then it would 
have to store the encoding information for al subsequent requests. It is a good 
idea to offer the option of entering the encoding and use the correct encoding 
to URLEncode the parameters. I can take a crack at this for the next release. 
does the idea of providing a text field for alternate encoding sound desirable 
or acceptable? Changing priority to low for now.

---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org