On Wed, Feb 3, 2016 at 9:43 AM, Yann Ylavic <ylavic....@gmail.com> wrote: > > I can't tell about the underlying HTTP data here, but I suspect there > is more than a single HTTP request sent by the client, which makes > httpd believe requests are pipelined, and hence never flush its output > until the client stops pipelining requests. > The client is now blocked waiting for the first response...
I forgot to ask, when it works (either with your patch on 2.4.18 or with 2.4.12), is the next (keepalive) request triggering an error message (in the log) or not? > > Regards, > Yann.
