httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Trawick <trawi...@bellsouth.net>
Subject Re: [PATCH] filtering and canned error responses
Date Thu, 07 Sep 2000 14:36:11 GMT
Tony Finch <dot@dotat.at> writes:

> rbb@covalent.net wrote:
> >
> >Well, this is where things start to get a little complicated, because we
> >have decided to distinguish between content generators and content
> >filters.  All of our generators are implemented as handler functions,
> >while filters are obviously implemented as filters.  What are error
> >messages?  Obviously, they are generated content, but they can't really be
> >implemented as handlers, because we are past the handler phase.  So, this
> >leaves us with two options.
> >
> >1)  A filter that soaks up input and replaces it with the error page.
> >2)  A completely separate function that co-opts the request processing,
> >and sets up a new filter stack.
> 
> This is called an internal redirect, isn't it? When an error occurs it
> causes an internal redirect to an error page URL which either results
> in internally generated content from the error document content
> handler, or if an ErrorDocument has been configured then you get
> another internal redirect to the page on disk.

If there is "ErrorDocument nnn URI" specified, there is an internal
redirect.  Without that type of ErrorDocument coded, there is no
internal redirect.

> I.e. make subrequests work and error documents will fall out in the
> wash :-)

Alternate view: make subrequests work and one of the three types of
error documents will fall out in the wash.


-- 
Jeff Trawick | trawick@ibm.net | PGP public key at web site:
     http://www.geocities.com/SiliconValley/Park/9289/
          Born in Roswell... married an alien...

Mime
View raw message