DO NOT REPLY [Bug 32296] - HTTP Header Content-Type always ISO-8859-1 under debian (browsers no longer detect encoding correctly - worked perfectly under redhat9)
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 --- Additional Comments From [EMAIL PROTECTED] 2005-04-04 20:13 --- see also Bug 34291 for a related issue -- 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]
DO NOT REPLY [Bug 32296] - HTTP Header Content-Type always ISO-8859-1 under debian (browsers no longer detect encoding correctly - worked perfectly under redhat9)
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 --- Additional Comments From [EMAIL PROTECTED] 2004-11-25 21:22 --- in Struts, using controller contentType=text/html; charset=UTF-8 in my struts-config.xml as per Bug 32396 More also in http://www.mail-archive.com/tomcat-user%40jakarta.apache.org/msg141816.html -- 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]
DO NOT REPLY [Bug 32296] - HTTP Header Content-Type always ISO-8859-1 under debian (browsers no longer detect encoding correctly - worked perfectly under redhat9)
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]
DO NOT REPLY [Bug 32296] - HTTP Header Content-Type always ISO-8859-1 under debian (browsers no longer detect encoding correctly - worked perfectly under redhat9)
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|REOPENED|RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2004-11-19 15:52 --- That has no place in our docs. It's not a Tomcat issue. Please don't reopen this item. -- 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]
DO NOT REPLY [Bug 32296] - HTTP Header Content-Type always ISO-8859-1 under debian (browsers no longer detect encoding correctly - worked perfectly under redhat9)
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 --- Additional Comments From [EMAIL PROTECTED] 2004-11-19 16:05 --- Finally solved it at least partially on the jsp level since I couldn't convince tomcat to do it: each jsp needs a %@ page contentType=text/html; charset=UTF-8 % if I only do %@ page contentType=text/html % it remains on ISO-8859-1 as before. The remaining problem is that the contents coming from the DB are now wrong while the static jsp content is correct (the jsp's being saved as UTF) If I also set %@ page pageEncoding=ISO-8859-1 % on each page, the static and DB content are now the same again, but unfortunately, both wrong while the http header is correct. Anyway, I have also removed struts from my app and built a comparably small war-File (0.5 MB) I am willing to share if anybody is interested. Also, if others run into that issue too, here a log of some futile attempts to solve it within tomcat: - as per void org.apache.catalina.util.CharsetMapper.addCharsetMappingFromDeploymentDescriptor(String locale, String charset), it appeared, that the redhat locale is not present in apache.catalina.util.CharsetMapperDefault.properties - setting in the catalina.sh export CHARMAP=UTF-8 export LANG=dummy export LC_ALL=du_MY export LANGUAGE=du to intentionally creating the suspected miss did not do it. - migrating the web.xml to http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd and adding /welcome-file-list locale-encoding-mapping-list locale-encoding-mappinglocaleen/localeencodingUTF-8/encoding/locale-encoding-mapping ... didn't apparently solve it either. - since I use struts with redirect, setting for a single page response.setHeader(Content-Type, text/html;charset=UTF-8); didn't help either. - exchanging the CharsetMapperDefault.properties in the catalina.jar with an utf-ed verison didn't help either. - exchanging the Constants.class in the tomcat-coyote.jar with DEFAULT_CHARACTER_ENCODING=UTF-8 didn't help either. - exchanging the LocaleToCharsetMap.class in the tomcat-coyote.jar an utf-ed verison didn't help either. -- 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]
DO NOT REPLY [Bug 32296] - HTTP Header Content-Type always ISO-8859-1 under debian (browsers no longer detect encoding correctly - worked perfectly under redhat9)
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
--- Additional Comments From [EMAIL PROTECTED] 2004-11-19 18:38 ---
now, I got it to work, albeit in an ugly way:
in void org.apache.coyote.http11.Http11Processor.prepareResponse()
instead of
headers.setValue(Content-Type).setString(contentType);
do
if (contentType.startsWith(text/html)) {
headers.setValue(Content-Type).setString(
text/html;charset=UTF-8);
} else {
headers.setValue(Content-Type).setString(contentType);
}
and then replace that class in tomcat-http11.jar and all works fine (obviously
only for a site that serves all html pages in UTF-8).
Conclusion: Either it is a bug, or there must be another option to determine the
charset of the HTTP header that is not really obviously documented.
--
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]
DO NOT REPLY [Bug 32296] - HTTP Header Content-Type always ISO-8859-1 under debian (browsers no longer detect encoding correctly - worked perfectly under redhat9)
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|CLOSED --- Additional Comments From [EMAIL PROTECTED] 2004-11-19 19:39 --- A few comments that might help (although this is really a tomcat-user discussion and has no place on bugzilla) - useBodyEncodingForURI=true URIEncoding=UTF-8 affect request processing and have nothing to do with the content-type sent to the browser - have you read the spec, specifically the errata http://www.jcp.org/aboutJava/communityprocess/maintenance/jsr053/errata_1_2_a_ 20020321.html? As you will see, Tomcat is implementing the spec. I think you need to set both the content-type AND the page encoding. If you wish to discuss further, I am happy to discuss this but ONLY on the tomcat- user mailing list. -- 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]
