You are viewing a plain text version of this content. The canonical link for it is here.
Posted to docs@httpd.apache.org by Rich Bowen <rb...@rcbowen.com> on 2001/09/09 20:54:18 UTC
server-parsed
Does the server-parsed handler go away completely in version 2.0, to be
replaced by the INCLUDES filter?
--
Nothing is perfekt. Certainly not me.
Success to failure. Just a matter of degrees.
---------------------------------------------------------------------
To unsubscribe, e-mail: apache-docs-unsubscribe@apache.org
For additional commands, e-mail: apache-docs-help@apache.org
Re: server-parsed
Posted by Ryan Bloom <rb...@covalent.net>.
On Sunday 09 September 2001 11:54, Rich Bowen wrote:
> Does the server-parsed handler go away completely in version 2.0, to be
> replaced by the INCLUDES filter?
Nope. That handler still works. :-)
Ryan
--
______________________________________________________________
Ryan Bloom rbb@apache.org
Covalent Technologies rbb@covalent.net
--------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: apache-docs-unsubscribe@apache.org
For additional commands, e-mail: apache-docs-help@apache.org
Re: server-parsed
Posted by "William A. Rowe, Jr." <wr...@rowe-clan.net>.
From: "Rich Bowen" <rb...@rcbowen.com>
Sent: Sunday, September 09, 2001 2:02 PM
> I have a related question, however. Why are AddOutputFilter and
> SetOutputFilter in different modules? Don't they do very similar
> things? Is there something more fundamental that I am missing WRT the
> arrangement of various things in various places.
No they don't. This was even broken with SetHandler until I moved it a few
weeks back.
AddOutputFilter _only_ works if mime negotation (mod_mime) runs. If the user
disables mod_mime, AddOutputFilter is also disabled.
SetOutputFilter (and SetHandler as of 2.0.25, for that matter) can be used
without mod_mime, and will be by some users. It has nothing to do with mime
negotation, and (in the case of filters) may be used to set filters in addition
to the mime AddOutputFilters.
Bill
---------------------------------------------------------------------
To unsubscribe, e-mail: apache-docs-unsubscribe@apache.org
For additional commands, e-mail: apache-docs-help@apache.org
Re: server-parsed
Posted by Cliff Woolley <jw...@virginia.edu>.
On Sun, 9 Sep 2001, Rich Bowen wrote:
> On Sun, 9 Sep 2001, Rich Bowen wrote:
>
> > Does the server-parsed handler go away completely in version 2.0, to be
> > replaced by the INCLUDES filter?
>
> I'm sorry. Silly question. I see that it does. Somehow, in my long
> absence, I missed that.
It was gone for a while, but it came back for backward compatibility. If
you use server-parsed, it just inserts the INCLUDES filter into the chain
for you and punts to the default handler.
--Cliff
--------------------------------------------------------------
Cliff Woolley
cliffwoolley@yahoo.com
Charlottesville, VA
---------------------------------------------------------------------
To unsubscribe, e-mail: apache-docs-unsubscribe@apache.org
For additional commands, e-mail: apache-docs-help@apache.org
Re: server-parsed
Posted by Rich Bowen <rb...@rcbowen.com>.
On Sun, 9 Sep 2001, Rich Bowen wrote:
> Does the server-parsed handler go away completely in version 2.0, to be
> replaced by the INCLUDES filter?
I'm sorry. Silly question. I see that it does. Somehow, in my long
absence, I missed that.
I have a related question, however. Why are AddOutputFilter and
SetOutputFilter in different modules? Don't they do very similar
things? Is there something more fundamental that I am missing WRT the
arrangement of various things in various places.
--
Nothing is perfekt. Certainly not me.
Success to failure. Just a matter of degrees.
---------------------------------------------------------------------
To unsubscribe, e-mail: apache-docs-unsubscribe@apache.org
For additional commands, e-mail: apache-docs-help@apache.org