Bug 15406 - error-page responses are sent with wrong status code!
Summary: error-page responses are sent with wrong status code!
Status: RESOLVED INVALID
Alias: None
Product: Tomcat 4
Classification: Unclassified
Component: Catalina (show other bugs)
Version: 4.1.12
Hardware: All All
: P3 major (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-12-16 18:16 UTC by Donald Ball
Modified: 2004-11-16 19:05 UTC (History)
0 users



Attachments
here is a patch against cvs head from 2002-12-30 (2.08 KB, patch)
2002-12-30 16:16 UTC, Donald Ball
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Donald Ball 2002-12-16 18:16:33 UTC
I recently had occasion to use the error-page facility of web.xml with tomcat
4.x for the first time. To my surprise, tomcat sends a 200 status code with the
content, regardless of what the original error code is! As far as I can tell,
this is totally incorrect behavior. I regard it as a "major" bug because it's
essentially "censoring" the http conversation between client and webapp, and
makes it impossible for search engines, et. al., to distinguish between good and
bad urls.

I have verified this behavior in jakarta-tomcat-4.0.6 and 4.1.12 in standalone
mode. I have not tested it with any of the connectors. I am happy to help
contribute a patch if the developers agree this is a bug but have not the time
to fix it.
Comment 1 Donald Ball 2002-12-30 16:16:53 UTC
Created attachment 4297 [details]
here is a patch against cvs head from 2002-12-30
Comment 2 Donald Ball 2003-01-15 17:15:03 UTC
craig insists that the current behavior is correct, that it's the responsibility
of the referred resource to set the response code.