httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Greg Ames <grega...@raleigh.ibm.com>
Subject Re: [PATCH] filtering and canned error responses
Date Tue, 12 Sep 2000 16:25:22 GMT
Tony Finch wrote:
> 
> There does need to be a further fallback in case of egregious 500
> errors, e.g. when setting up the filter stack for an error, in which
> case there will have to me a hard-coded oh-my-god-everything's-broken
> filter stack probably comprising nothing but the core filter and an
> implementation -> network charset filter if necessary.

OK - why don't we get rolling on the fallback piece since we need it no
matter what?  

Incidently, last night I was Google-ing trying to find a good price on a
Martin Backpacker guitar.  I found a link to a site which was served by
Apache (yay!) but the page I wanted was missing (boo!).  I got the
canned error message for a 404, then down at the bottom it said,
"Additionally, a <blah> error was encountered while trying to use an
ErrorDocument to handle the request."  I'm guessing that the site was
moved to a machine with a different file structure, and then the config
file was copied over without adjusting the ErrorDocument directives.

The point here is that if we redirect to handle an error, and the
redirect fails for whatever reason, we need to report the original error
and not just report a 500.  Otherwise we are regressing function that
worked prior to filtering.

I'll take a look at Jeff's patch this afternoon and see if it seems
appropriate for the worst case scenarios.

Greg

Mime
View raw message