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=13231>.
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=13231

web container not sending back content type if html <META> is in JSP

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |



------- Additional Comments From [EMAIL PROTECTED]  2002-10-03 06:18 -------
same thing happens when Netscape is used.
The same bug does not occur when IE and Netscape are used to access the same 
pages served by other appservers from IPlanet, Weblogic, Oracle.

If the response html (of the JSP) is saved into a .html and reopened in either 
browser, auto-selecting of the encoding as gb2312 occurs.

I suspect that the HTTP response returned by tomcat remains at 
  Content-Type: text/html;charset=ISO-8859-1
even though the html <META> is present, forcing the browser to use the ISO 
encoding.

would appreciate if you will look into this, or forward it to the correct 
module I/C, cos' it quite irritating to have to change the encoding manually 
upon every page access.

thanks.

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

Reply via email to