Hi William,
> * In the first connection stream you can see the initial document,
> followed by the event stream
> * Then you can see the client has used http piping (pretty dumb
> considering the browser should know this connection is occupied)
> to send requests for /21.png /22.png /23.png ( the hanging resources)
What we can see is that the client asks for /events and the server
responds with a "Transfer-Encoding: chunked" response, in multiple
different TCP packets.
While the server continues to send more and more chunks as a response
to /events, the client fires the requests for /21.png /22.png /23.png.
This may be upsetting haproxy (I'm attaching a pcap with the (single) tcp
session I'm talking about, extracted from ios-haproxy.pcap).
I'm not really familiar with the RFCs when it comes to chunked encoding
and especially pipelining (let alone when combining those two).
William, what exact release are you using? Could you confirm that tunnel
mode fixes your issue ("option http-tunnel" in the default section)?
Regards,
Lukas
ios-haproxy-filtered.pcap
Description: Binary data
