-calvin
Calvin Smith wrote:
I am having trouble implementing a custom error page for a 403 authorization error.
My web.xml has the following:
<error-page> <error-code>403</error-code> <location>/authorizationError</location> </error-page>
And my main controller file has the following entry:
<page id="authorizationErrorID" path-info="/authorizationError" model="oxf:/config/authorizationError.xml"/>
And there is a simple xml file at oxf:/config/authorizationError.xml.
When I try to access an unauthorized page, I still get the default (ugly) Tomcat error page. I thought that the web.xml entry should redirect the app. to /authorizationError, which OXF would receive and process by return the xml file that is mapped to that URI in the controller file.
I see in the logs the following two entries:
/authorizationError - Received request
/authorizationError - Timing: 31 - Cache hits: 31, fault: 0, adds: 0, success rate: 100%
which looks like success to me, but the browser never gets forwarded to the correct URI, and the file referenced by that URI is not displayed either. Instead, I just get the standard Tomcat 403 error page.
Any idea what's going on?
thanks,
calvin
_______________________________________________ oxf-users mailing list [EMAIL PROTECTED] http://mail.orbeon.com/mailman/listinfo/oxf-users
_______________________________________________ oxf-users mailing list [EMAIL PROTECTED] http://mail.orbeon.com/mailman/listinfo/oxf-users
