Philip Martin <philip.mar...@wandisco.com> writes: > Lieven Govaerts <l...@mobsol.be> writes: > >> Is there a reason you specifically mention pipelined here? The first >> response has been handled so it's just synchronous communication. > > The point is that the client reads data from the server before sending > the second response. If the client were to close/reopen the connection > that data would get dropped, or at least that is what appears to happen > as I don't see the bug if the server sends "Connection: close" with the > first response.
My use of "pipelining" was incorrect here, what I mean is that both requests have to be sent on the same connection. I suppose it might be possible to trigger the bug with a single request if the server sends spurious data before receiving the request, but it might be tricky to get the timing right. -- Philip
