httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aryeh Katz" <>
Subject RE: ap_invoke_handler
Date Tue, 21 Oct 2003 17:11:47 GMT
> At 06:06 AM 10/21/2003, Tikka, Sami wrote:
> >>-----Original Message-----
> >>From: William A. Rowe, Jr. [] 
> >[...]
> >>Do not attempt to 
> >>remove a filter once it's inserted, simple force it to be 
> >>inert.  Serveral Apache filters already do this, although I 
> >>can't name one offhand (SSL might be, I think.)
> >
> >???? Perhaps I am just missing something, but is there something
> >wrong in removing a filter, perhaps by itself, using
> >ap_remove_input/output_filter()
> Once *one* byte of data has passed through a given filter within the
> filter chain, you cannot know if one filter is sitting on bytes of
> request or response body that it is waiting for completion.  Maybe it
> has a partial token stored, maybe it's an incomplete multibyte
> sequence for a given code page translation. In both cases, once a byte
> is inside the filter chain, during a request (this is what I'm
> assuming your module does) you cannot add and drop filters.
In my input filter, I don't pass ANY data on until I am sure all the filter 
processing is done (the filter is only inserted selectively). What would be 
wrong with calling remove_filter then? It was inserted when required, and 
when I'm ready to return (and pass some data on), remove the filter I just 
> Those APIs are used for changing the filters before the request is
> processed. 

Aryeh Katz
Secured-Services Inc.

View raw message