I have been trying out 4.1.0. I have noticed that if you do not specify the language attribute in the page directive then the contentType attribute has no effect on the page encoding.
If I do this: <%@ page contentType="text/html; charset=Shift_JIS" %> and then look at generated source code for the servlet, I notice that the content type on the response is set properly but the source code hasn't been converted from shift jis to utf8. However if I do this: <%@ page language="java" contentType="text/html; charset=Shift_JIS" %> Everything works fine. The contentType attribute worked with or without a language attribute in 4.0.3. -----Original Message----- From: Remy Maucherat [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 30, 2002 6:50 PM To: Tomcat Developers List Subject: [4.1.0] Anyone testing it ? Is anyone testing 4.1.0 ? The URL as a reminder: http://jakarta.apache.org/builds/jakarta-tomcat-4.0/test/v4.1.0/ Obviously, I expect people voting to rate the build to have tried it ;-) Of particular interest is testing: - AJP 1.3 support - To see if bug 5735 is fixed with the current Coyote connector - Jasper 2 Thanks, Remy -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
