DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=32296>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=32296 Summary: HTTP Content-Type always ISO-8859-1 under debian (browsers no longer detect encoding correctly - worked perfectly under redhat9) Product: Tomcat 5 Version: 5.0.28 Platform: PC OS/Version: Windows XP Status: NEW Severity: normal Priority: P2 Component: Unknown AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] CC: [EMAIL PROTECTED] when using redhat, everything worked fine and https://www.privasphere.com/index_de.jsp got decoded correctly by MSIE or recent mozilla. after moving to debian (latest stable), it no longer works: http://bugs.privasphere.com:8443/index_de.jsp (took away ssl and compression to make it better sniffable). The browsers think it is ISO-8859-1 and only after a manual change to UTF-8, the umlauts show up correctly (for one page only). As per all the bugs referenced in http://jakarta.apache.org/tomcat/faq/misc.html#tomcat5CharEncoding and the discussion in http://marc.theaimsgroup.com/?l=tomcat-user&m=108905503431227&w=2 I did try to add <<useBodyEncodingForURI="true" URIEncoding="UTF-8">> to my server.xml with no effect. on Redhat, my System.getProperty("file.encoding") yields ISO-8859-1 while on Debian first, it was ANSI_X3.4-1968, then I successively on the operating system level with /etc/environments and inside the servlet init() (System.setProperty("file.encoding", ...)), I set it to ISO-8859-1 and UTF-8 - no effect. Is there another way to influence the HTTP header's? On debian, I still get <<HTTP/1.1 200 OK Content-Type: text/html;charset=ISO-8859-1 Content-Length: 6078 Date: Thu, 18 Nov 2004 18:35:11 GMT Server: Apache-Coyote/1.1>> While on the redhat server (I'll only be able to sniff without SSL tomorrow), I suspect this to be UTF-8? Or are there other reasons the browser could miss the page encoding albeit the browser-view-source shows no relevant differences in the page source? I fear that this bug gets closed invalid immediately as many before, but hopefully, it leads to some insight that could enhance the documentation or FAQ such that less people will not fall into this trap (so probably, this is an RFE) -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
