https://issues.apache.org/bugzilla/show_bug.cgi?id=51653
--- Comment #3 from Stephan Maminakis <maminakis.step...@ensco.com> 2011-09-26
17:48:19 UTC ---
Mark,
I have just upgraded from 7.0.20 to 7.0.21 and I think this resolution has
affected a very simple error page that I have had in my web app since Tomcat 5.
We have our own Realm which hits our Oracle database for the appropriate
roles.
I have the following in my web.xml:
<error-page>
<error-code>403</error-code>
<location>/badaccess.html</location>
</error-page>
...
<security-constraint>
<web-resource-collection>
<web-resource-name>myadmin</web-resource-name>
<description>My Admin Application</description>
<url-pattern>/myadmin/*</url-pattern>
<http-method>GET</http-method>
<http-method>POST</http-method>
</web-resource-collection>
<auth-constraint>
<description>System Administrators</description>
<role-name>system_admin</role-name>
</auth-constraint>
</security-constraint>
The badaccess.html page lives in my web app (war) and simply displays a nice
message to the user, letting him know he is going to an off-limits page. Since
I have upgraded to 7.0.21 this no longer works. Instead, I get the standard
Tomcat 403 error page. Does the resolution to this issue require me to do
something differently? Again, this worked fine up until 7.0.20.
Thanks for any help,
Stephan
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
