Haven't had an opportunity to look over the fixes or give them a try. Everything...
Just keeping people apprised of my work on this. For the second time, HTTP state...
An example of what I'm investigating for a workaround: diff -r 4c25fb239336 curl/lib/multi.c...
What I've been seeing disagrees with the above description so I dug in with the debugger...
Is that because the connection is closed or because canceling the single request...
I wonder if there's a non-pipelined scenario where this is a problem as well: request...
Pipelining + client-side timeouts lead to loss of synchronization with response stream and incorrect data delivery
b) would be my preference. a) is harsh in any scenario, to do it without corrupting...