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=11366>. 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=11366 Handling of Wrapped Responses Summary: Handling of Wrapped Responses Product: Tomcat 4 Version: 4.0.3 Final Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Normal Priority: Other Component: Unknown AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] When forwarding a request to a resource that sets status HttpServletResponse.SC_NOT_FOUND the server treats wrapped responses differently from unwrapped responses: For an unwrapped response 404 is correctly signalled to the web browser, while with a wrapped response the browser waits indefinitely (IE 5.5) or signals an empty response (Netscape 4.6). wget on the other hand does seem to recognize the 404 in both cases correctly. I'll include an example app. If you install it and click on links 1. and 2. you'll see 404. When clicking on link 3. you'll see the phenomenon described above. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
