Owa_custom and 403 Forbidden

Question

In my web application, I am using owa_custom to check and set cookies for authorization. All this is working nicely.
When owa_custom returns false, it redirects to 403 Forbidden and execution stops. Is there a way alter what the 403 pages looks like?
I’ve tried using owa_util.redirect_url() to go to a custom 403 page, the problem is that execution after the redirect continues. Looks like the only way possible to halt execution is to return false out of the owa_custom procedure.
So is it possible to alter the defaut 403 Forbidden page?
Edited by: brian.mcginity on Dec 22, 2009 6:51 PM

Answer 1

As far as I know, that needs to be done on the web server itself - customising the error pages for the various http error codes.
In Apache for example, the httpd.conf file you can configure the http response accompanying an http error code, using the ErrorDocument+ option, as follows (from the Apache version that shipped with the APEX version I'm using):
# Customizable error response (Apache style)
#  these come in three flavors
#    1) plain text
#ErrorDocument 500 "The server made a boo boo.
#  n.b.  the single leading (") marks it as text, it does not get output
#    2) local redirects
#ErrorDocument 404 /missing.html
#  to redirect to local URL /missing.html
#ErrorDocument 404 /cgi-bin/missing_handler.pl
#  N.B.: You can redirect to a script or a document using server-side-includes.
#    3) external redirects
#ErrorDocument 402 http://some.other_server.com/subscription_info.html
#  N.B.: Many of the environment variables associated with the original
#  request will *not* be available to such a script.