DO NOT REPLY [Bug 24385] - text conversion fails with jsp:forward/param on linux server
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=24385. 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=24385 text conversion fails with jsp:forward/param on linux server [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WORKSFORME --- Additional Comments From [EMAIL PROTECTED] 2003-11-09 19:33 --- I have tested TC4-Head and TC5-Head on windows and your test case passes. Given the lack of clarity in the JSP1.2 spec and that setting the request encoding works for you in TC4 I am closing this bug as worksforme. Please re- open it if you find the problem still exists in TC5 on the linux/windows combination. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 24385] - text conversion fails with jsp:forward/param on linux server
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=24385. 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=24385 text conversion fails with jsp:forward/param on linux server --- Additional Comments From [EMAIL PROTECTED] 2003-11-07 09:15 --- Thank you for your answer. I've tried the first proposion: % request.setCharacterEncoding(ISO-8859-1); % gives strange results, but % request.setCharacterEncoding(UTF-8); % works (on the other hand the workaround fails). Result - Template Text: Test Umlaut Ä-Ö-Ü-ä-ö-ü Text from Parameter: Test Umlaut Ä-Ö-Ü-ä-ö-ü Text from Parameter (Workaround): Test Umlaut ?-?-?-?-? - Without setCharacterEncoding the system browser/tomcat seems to do the conversion ISO-8859-1 to UTF-8 twice in one direction, but only once in the other. For me the workaround does the job at the moment - so I wait for Tomcat 5. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 24385] - text conversion fails with jsp:forward/param on linux server
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=24385. 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=24385 text conversion fails with jsp:forward/param on linux server --- Additional Comments From [EMAIL PROTECTED] 2003-11-06 21:33 --- request.getParameter() uses the request encoding when reading the parameters, while jsp:param in 4.1.x encodes the parameter with URLEncoder.encode(String), which uses the platform default encoding. If they are different, you'll likely get problem like this. Try setting the request encoding to the platform default encoding by inserting a % request.setCharacterEncoding(ISO-8859-1); % at the beginning of test1.jsp. Alternately, you can also use JSTL: fmt:requestEncoding value=ISO-8859-1/ This bug is unlikely to get fixed for 4.1.x, since the JSP 1.2 spec is unclear regarding parameter encodings. JSP 2.0 specifies that the jsp:param values should be encoded with the request encoding, so Tomcat 5 might work better for you. Since most browsers do not set request encodings, you are still advised to explictily set it with request.setCharacterEncoding(), but then you can set it anything other than the platform default, such as UTF-8. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
