DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=18040>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=18040 Entering <error-page> in web.xml for error code 401 BASIC unexpected behaviour [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 2004-05-10 20:48 ------- The 401 response is actually part of the BASIC authentication process (see RFC 2616 for full details) as well as the response when BASIC authentication fails. This specification of an error page for 401 interfers with this dual use. 401 should perhaps be a special case but the servlet spec does not treat it as such. The work-around described above (or something that achieves the same thing) is the way to go if you want a custom error page for a 401. Strictly this bug report is INVALID as tomcat is doing what the spec says it should. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
