httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ryan Bloom <>
Subject Re: cvs commit: httpd-2.0/modules/filters mod_include.c
Date Sun, 26 Aug 2001 03:16:38 GMT
On Saturday 25 August 2001 20:06, William A. Rowe, Jr. wrote:
> From: "Joshua Slive" <>
> Sent: Saturday, August 25, 2001 9:23 PM
> > Before I go back and put back all the stuff I took out of the docs on
> > mod_include handlers (;-) could you clarify this a little for me.
> >
> > 1. True/False:  Using the handler is perfectly equivalent to using the
> > filter except in the case where more than one filter or handler is in use
> > or a content-type other than text/html is being filtered.  The
> > server-parsed handler cannot be used when another handler is in use for
> > the same file (eg. cgi-script).  As well, the server-parsed handler will
> > always run first, so if you wish the INCLUDES filter to run after another
> > filter, you should explictly specify the filter chain using SetFilter.
> > Finally, the server-parsed filter will always output HTML, whereas the
> > INCLUDES filter can process any file type and will not change the
> > content-type.
> Actually, they are very different.  I don't know which we will endorse.
> I'd expect performance testing to answer the question...

I only added the AddType stuff back for backwards compat.  The handler
doesn't actually exist.  We just use the handler as a way to tell mod_include
to add the filter to the chain.  If you use the handler, the INCLUDES filter
will always run immediately after the default-handler

> > 3. If you are going to add back the magic-mime-type, please let me know
> > so I don't have to re-re-revise the docs.
> Dunno those plans

I am likely to add it back in sometime this weekend.


Ryan Bloom               
Covalent Technologies

View raw message