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=6488>. 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=6488 Error: 304. Apparent bug in default ErrorHandler code. Summary: Error: 304. Apparent bug in default ErrorHandler code. Product: Tomcat 3 Version: 3.3 Final Platform: All OS/Version: All Status: NEW Severity: Major Priority: Other Component: Servlet AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I just stumbled upon a show-stopper problem with Tomcat 3.3a and Apache mod_jk. When refreshing JSPs that referenced static resources (i.e. a CSS stylesheet or images), from time to time junk would appear at the top of the page, saying "Error: 304... Location: <page address>". The said static resources would not load and the browser would appear to hang indefinitely. I tracked the problem to the method StatusHandler.doService defined in share/org/apache/tomcat/modules/generators/ErrorHandler.java When the 304 (Not Modified) condition is encountered, this method generates a message body with the above mentioned "junk" and returns it to mod_jk. RFC 2068 states: "If the client has performed a conditional GET request and access is allowed, but the document has not been modified, the server SHOULD respond with this status code. The response MUST NOT contain a message-body." Replacing Tomcat's vanilla ErrorHandler with my own clone with the whole message body generating block omitted if sc == 304 eliminated the problem. Interestingly, the bug could only be demonstrated with mod_jk + Tomcat, but not when I was using Tomcat alone as a web server. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
