DO NOT REPLY [Bug 7602] - After RequestDispatcher.forward() the character encoding for parameters is set to ISO-8859-1

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
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=7602

After RequestDispatcher.forward() the character encoding for parameters is set to 
ISO-8859-1





--- Additional Comments From [EMAIL PROTECTED]  2002-10-28 13:28 ---
This continues to be a bug in 4.1.12.

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

DO NOT REPLY [Bug 7602] - After RequestDispatcher.forward() the character encoding for parameters is set to ISO-8859-1

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
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=7602

After RequestDispatcher.forward() the character encoding for parameters is set to 
ISO-8859-1





--- Additional Comments From [EMAIL PROTECTED]  2002-07-25 11:02 ---
Why use a default of "ISO-8859-1" or "UTF-8" ? Why don't use the page encoding 
defined by, e.g. <%@ page contentType="text/html; charset=Big5"%> on the page 
head ?

People always use same encoding across the whole application, even for 
internationisation they will choose whatever suitable encoding and fixed to use 
it across whole application.

As we, the Multi-byte character user, need to explicitly call 

request.setCharacterEncoding("BIG5");

before getting the passed in Chinese parameters for processing, or-else the 
parameters are decoded using "ISO-8859-1" uselessly.

Also, I suggest to add / change the code of method to facilitate for re-doing 
the parameter parsing using another encoding for the rare case that different 
encodings are required to use across application.

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

DO NOT REPLY [Bug 7602] - After RequestDispatcher.forward() the character encoding for parameters is set to ISO-8859-1

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
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=7602

After RequestDispatcher.forward() the character encoding for parameters is set to 
ISO-8859-1

[EMAIL PROTECTED] changed:

   What|Removed |Added

   Severity|Normal  |Enhancement
   Priority|Other   |Low



--- Additional Comments From [EMAIL PROTECTED]  2002-04-04 21:33 ---
This is unspecified i18n behavior (there is no recognized standard for this, or
any requirement in the spec). Tomcat will tend to default to UTF8 for req
parameters encoding in the future (probably in the next major release), which
could help a bit.

--
To unsubscribe, e-mail:   
For additional commands, e-mail: