[ http://issues.apache.org/jira/browse/TAPESTRY-607?page=comments#action_12375456 ]
Curtis Paris commented on TAPESTRY-607: --------------------------------------- I would suggest that this bug be reopened, and that the work around be removed. In debugging a UTF-8 issue on our new site, we came across this issue. Infact, I diagnosed it down to the same set of code in the Tomcat code base as the linked Tomcat bug. It wasn't until I had found the _tomcatPatch in ServletWebResponse, and the org.apache.tapestry.607-patch flag that I came across the ticket here. When using the work around, we are seeing that the Content-Type is no longer sent at all. This is very bad, and I think worse than the fact that it doesn't include the charset in the Content-Type. What we are doing: Our Logout.html page is hooking the pageBeginRender event. It throws a PageRedirectException to the login page. The login page activates and renders. Environment: Tomcat 5.5.16, Tapestry 4.0.1, JSDK 1.5.0 Incase you want to see the headers, using a sniffer, here is what we saw. In normal, we get "text/html;charset=UTF-8". In the Non-Workaround, we get "text/html". and with the work around, we get no Content-Type at all. ---------- NORMAL REQUEST TO LOGIN ------------ GET /Login.html HTTP/1.1 Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/x-shockwave-flash, application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword, */* Accept-Language: en-securid Accept-Encoding: gzip, deflate User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; InfoPath.1) Host: d-sfo-nix-cparis:8080 Connection: Keep-Alive Cookie: org.apache.tapestry.locale=fr_FR; HTTP/1.1 200 OK Server: Apache-Coyote/1.1 Set-Cookie: JSESSIONID=7F8998B4BFE5144F186FD71FF93E8989; Path=/ Content-Type: text/html;charset=UTF-8 Content-Length: 6719 Date: Fri, 21 Apr 2006 00:00:45 GMT <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd";> <!-- Application: PAC 2.0 --> <!-- Page: Login --> ---------- REQUEST TO LOGIN VIA THE LOG OUT PAGE, NO WORKAROUND ------------ GET /Logout.external?sp=SReportsSummary HTTP/1.1 Accept: */* Accept-Language: en-securid Accept-Encoding: gzip, deflate User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; InfoPath.1) Host: d-sfo-nix-cparis:8080 Connection: Keep-Alive Cache-Control: no-cache Cookie: org.apache.tapestry.locale=fr_FR; HTTP/1.1 200 OK Server: Apache-Coyote/1.1 Content-Type: text/html Content-Length: 6802 Date: Thu, 20 Apr 2006 23:55:53 GMT <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd";> <!-- Application: PAC 2.0 --> <!-- Page: Login --> ---------- REQUEST TO LOGIN VIA THE LOG OUT PAGE, WITH WORKAROUND ------------ GET /Logout.external?sp=SReportsSummary HTTP/1.1 Accept: */* Accept-Language: en-securid Accept-Encoding: gzip, deflate User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; InfoPath.1) Host: d-sfo-nix-cparis:8080 Connection: Keep-Alive Cache-Control: no-cache Cookie: org.apache.tapestry.locale=fr_FR; HTTP/1.1 200 OK Server: Apache-Coyote/1.1 Content-Length: 6802 Date: Thu, 20 Apr 2006 23:43:51 GMT <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd";> <!-- Application: PAC 2.0 --> <!-- Page: Login --> > Output encoding problem with some versions of Tomcat 5 > ------------------------------------------------------ > > Key: TAPESTRY-607 > URL: http://issues.apache.org/jira/browse/TAPESTRY-607 > Project: Tapestry > Type: Bug > Components: Framework > Versions: 4.0 > Environment: jdk1.4,tapestry4-beta5 > Reporter: Jone > Assignee: Howard M. Lewis Ship > Fix For: 4.0 > Attachments: tapestry-607.zip > > After upgrading my project from beta4 to beta5,the utf-8 encoded > Chinses,Japanese characters comes into "????".In fact ,the problem occurs in > continuous actived pages.For example,In page1,in direct lisener mehtod > invoke "cycle.active('page2')",then in page2,in pageBeginRender() invoke > "cycle.active(page3)",now in rendered page3,all the "utf-8" character comes > in to "????". -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
