DO NOT REPLY [Bug 26403] - double UTF-8 encoding of HTTP request parameters

2004-02-10 Thread bugzilla 
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=26403.
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=26403

double UTF-8 encoding of HTTP request parameters

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||LATER



--- Additional Comments From [EMAIL PROTECTED]  2004-02-11 03:50 ---
Marking as RESOLVE LATER pending a course of action.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 26403] - double UTF-8 encoding of HTTP request parameters

2004-01-24 Thread bugzilla 
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=26403.
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=26403

double UTF-8 encoding of HTTP request parameters





--- Additional Comments From [EMAIL PROTECTED]  2004-01-24 21:24 ---
some more comments:

I tried not only with the examples, but other forms as well. I also tried using
the i18n filter as described here:

http://www.anassina.com/struts/i18n/i18n.html

what I found is that the request object already has UTF-8 as the encoding type
when it gets to the filter, so the issue is not that the server doesn't know
what kind of encoding to use.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]