On Thu, Jun 30, 2011 at 09:11, Sorin Manolache <sor...@gmail.com> wrote: > On Thu, Jun 30, 2011 at 02:56, Jodi Bosa <jodib...@gmail.com> wrote: >> I'm encountering a strange interaction between modules (including my own). >> When I track it down, it appears that input filters are called after the >> handler is finished which results in 2 bodies in the response. >> >> In other words, this is what appears to be happening: >> Input filters called with AP_MODE_GETLINE (for each HTTP request >> header) >> Handler called and returns 302 >> input filters called with AP_MODE_READBYTES and 8192 >> >> >> I've placed logging in ap_internal_*_redirect() and removed all related >> modules to see if one was a problem - yet the same issue happens. >> >> Thanks for any help. >> > > > At the end of the request processing chain, apache places a function > that clears the request body. > (ap_finalize_request_protocol->ap_discard_request_body). > > Your inut filter should place an EOS bucket in the brigade or return > something else than APR_SUCCESS in this second invocation.
Or it should remove itself from the filter chain after the first invocation (in the handler). I haven't tried this one. S
