You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tomcat.apache.org by bu...@apache.org on 2003/03/28 02:13:46 UTC

DO NOT REPLY [Bug 18437] New: - jk2 encoding handling

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

jk2 encoding handling

           Summary: jk2 encoding handling
           Product: Tomcat 4
           Version: 4.0 Beta 1
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Connector:Coyote JK 2
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: mic-gosen@ns.inter-mic.co.jp


when jk2 is used as a connector between Apache 2 and Tomcat 4.1.X, it does not 
properly handle the <meta http-equiv="content-type" 
content="text/html";charset=EUC-JP"> tag. The html response page is always 
encoded as ISO 8859_1 and not as EUC-JP on .html files.  
With JSP files, I am able to set the content type, but the problem occurs 
with .html files.

Perhaps this situation may occur on other encodings??

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org