I'm currently having a small problem with Tomcat 4.1.18, which didn't exist in 
Tomcat 4.0.4.

The problem can be illustrated with a one liner JSP:

<%@ page contentType="text/html" %>

This one line spits out an HTTP header of Content-Type: text/html on Tomcat 
4.0.4

However, under 4.1.18, the following is spit out:

Content-Type: text/html;charset=ISO-8859-1

I need the former behaviour because these pages need to handle both GB2312-80 
and ISO-8859-1.  As such, I cannot have the character set explicitly set, and 
it also cannot be dynamically generated.  The locale information is 
determined when the <head></head> information is output, using a taglib.  By 
that time, the page directive has already been issued.  Also, the contentType 
field in the page directive cannot be dynamic from what I've been able to 
determine. (Tomcat 3.xx)  Has this behaviour changed in 4.0.x/4.1.x?

Thanks.

Daniel

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

Reply via email to