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 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | Summary|HTTP Content-Type always |HTTP Header Content-Type |ISO-8859-1 under debian |always ISO-8859-1 under |(browsers no longer detect |debian (browsers no longer |encoding correctly - worked |detect encoding correctly - |perfectly under redhat9) |worked perfectly under | |redhat9) ------- Additional Comments From [EMAIL PROTECTED] 2004-11-19 09:33 ------- so a Redhat HTTP header analysis: <<HTTP/1.1 200 OK Content-Type: text/html Connection: close Vary: Accept-Encoding Date: Fri, 19 Nov 2004 08:09:12 GMT Server: Apache-Coyote/1.1>> e.g. by "tcpflow -i eth0 port 8443" or http://livehttpheaders.mozdev.org shows: ==> under Redhat no "charset=..." is sent at all, thus it appears that in this case, the browsers decide upon the encoding stated in the page content Therefore, please document which environment variable drives coyote's HTTP header Content-Type charset. -- 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]
