httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William A. Rowe, Jr." <wr...@rowe-clan.net>
Subject RE: [PATCH] invalid HTTP status codes in access log
Date Fri, 22 Mar 2002 23:27:15 GMT
At 05:19 PM 3/22/2002, Ryan wrote:

>You don't know that something really broke just because the filter had a
>problem.

Ok, I'm confused.  If the filter has a problem, but it doesn't hurt anything,
why on earth would it report the error?

>I have written Apache filters (for 1.3) that decided
>authentication based on content in the request/response files.  All you
>know when the filter returns is what it tells you.  In this case, all it
>can tell you is the HTTP response code.  The filter should do the right
>thing with the error code, because the core can't know what an error
>code from a filter means.

It seems to me [I might be really confused] that the filter stack
is often too late to make these determinations.  If we send
a 200 header response, and the filter stack goes belly-up
or decides it doesn't like what its parsing, what can we do at
that point.

Even if you did try morphing the response code in the filter
stack, what would happen with custom error responses, etc?
Seems like things aren't recoverable at that point.

Bill


Mime
View raw message