owa_custom and 403 Forbidden
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