Re: Handling 500-Internal Server error caused by lackofauthority at the object level

-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx 
[mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of 
Matt.Haas@xxxxxxxxxxx
Sent: Friday, June 16, 2006 2:00 PM
To: web400@xxxxxxxxxxxx
Subject: Re: [WEB400] Handling 500-Internal Server error 
caused by lackofauthority at the object level

The error messages are customizable and you could even write 
a Net.Data
macro or a CGI program that is called which could look at the 
URL and do
whatever you want (I did this on our B2B shopping site to get 
different
looking 401 and 403 error pages for each virtual directory). 

Not sure I understand this.  Doesn't it conflict with your next
statement?

You're
basically restricted to the HTTP headers as far as information goes so
short of writing your own error handling module, you're not likely to
get enough info back to tell you it was an authority issue.

This is what I was afraid of.

What I was hoping for was someplace in the apache configuration that
would allow me to specify an error handling procedure or something.
Couldn't that error handler look back through the job log for the
CPF9821 - Not Authorized message and indicate some other error page to
send back to the browser.

Thanks,

Charles Wilt