You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by "Roy T. Fielding" <fi...@kiwi.ICS.UCI.EDU> on 2000/08/17 20:15:42 UTC
Re: [PATCH] ap_add_filter
>In other words... only filters of a certain TYPE can 'insert'
>filters of the SAME TYPE immediately after themselves
>or your stack might get messed up. I don't see any filter
>type checking in the patch.
That would be wrong. The only difference between a transfer coding
filter for deflate and a content coding filter for deflate is when
and where in the chain the filter is inserted. It is always possible
for the server to be misconfigured, causing filters to be inserted in
the wrong order: the result will be garbage. We don't need to
prevent people from implementing garbage.
....Roy
Re: [PATCH] ap_add_filter
Posted by rb...@covalent.net.
On Thu, 17 Aug 2000, Roy T. Fielding wrote:
> >In other words... only filters of a certain TYPE can 'insert'
> >filters of the SAME TYPE immediately after themselves
> >or your stack might get messed up. I don't see any filter
> >type checking in the patch.
>
> That would be wrong. The only difference between a transfer coding
> filter for deflate and a content coding filter for deflate is when
> and where in the chain the filter is inserted. It is always possible
> for the server to be misconfigured, causing filters to be inserted in
> the wrong order: the result will be garbage. We don't need to
> prevent people from implementing garbage.
++1!
Ryan
_______________________________________________________________________________
Ryan Bloom rbb@apache.org
406 29th St.
San Francisco, CA 94131
-------------------------------------------------------------------------------