On Tue, Oct 20, 2015 at 4:24 AM, Andy Wang <[email protected]> wrote: > > > On 10/19/2015 07:44 PM, Eric Covener wrote: >> >> On Mon, Oct 19, 2015 at 7:05 PM, Yann Ylavic <[email protected]> wrote: >>> >>> This is the deferred write triggering *after* the keepalive timeout, >>> whereas no subsequent request was pipelined. >>> I wonder if we shouldn't issue a flush at the end of each request when >>> the following is not already there, ie: >> >> >> Can you describe what breaks the current code? It looks like it's >> already trying to handle this case, I couldn't tell the operative >> difference. >> > > I'm also curious why it is that I seem to only be able to reproduce it with > a particular client. i would have expected using ncat to simulate the exact > same request would have been able to trigger the same behavior. > > And why is this only occurring on windows?
Yes, a complete misinterpretation on my side! The issue must be somewhere in mod_deflate (EOS handling?), since the flush done at connection level is of no help for the request filters. Will look at this...
