On Tue, Jun 30, 2015 at 8:53 PM, Plüm, Rüdiger, Vodafone Group <ruediger.pl...@vodafone.com> wrote: > > >> -----Ursprüngliche Nachricht----- >> Von: Eric Covener [mailto:cove...@gmail.com] >> Gesendet: Dienstag, 30. Juni 2015 20:09 >> An: Apache HTTP Server Development List >> Betreff: Re: option to block async write completion? >> >> On Fri, Jun 19, 2015 at 10:03 AM, Eric Covener <cove...@gmail.com> >> wrote: >> >> Maybe make MAX_REQUESTS_IN_PIPELINE configurable and use 1 in your >> case? >> > >> > that's interesting, will check it out. >> >> This turned into a bot of a pain when I realized just using a flush >> bucket accomplishes the same thing (everything up to the flush bucket >> is blocking) > > Are you sure that works with every filter in between? As far as I remember > some filters (mod_deflate?) just drop everything once they have seen EOS / > EOR.
At least ap_http_filter() does...
