You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tomcat.apache.org by bu...@apache.org on 2001/10/25 19:03:17 UTC

DO NOT REPLY [Bug 4413] - Error 403 doesn't work witrh JDBCRealm

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=4413>.
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=4413

Error 403 doesn't work witrh JDBCRealm

remm@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED



------- Additional Comments From remm@apache.org  2001-10-25 10:03 -------
That problem should have been fixed in 4.0.1.

Tomcat now allows setting error pages for almost error code that occurs after 
going through the host level, including:
- sendError sent from a forwarded request
- errors retrned by realms (401 or 403)
- mapping errors at the context level

It also includes an easy way to know if you can use an error page: if the fancy 
error report is displayed (you'll know what I'm talking about when you see it), 
then you can set an error page.