Hi Luke,
I finally managed to kill them all, and everything works fine for me.
It was indeed caused by late frames triggering GOAWAY, while we were
missing some info to determine if the frame was violating the protocol
or just a late response.
I've also found a few erroneous state transitions and an issue affecting
trailers which could also break the connection. For now it's only in
2.0-dev because it'll take me a while to collect all pending patches for
the next 1.9.
If you want to give it a try, it's here :
http://git.haproxy.org/?p=haproxy.git;a=snapshot;h=master;sf=tgz
I'm going to put this on haproxy.org and see if the request errors
get lower or not (it's not high anymore though and comparable to what
it was in H1 only).
Cheers,
Willy
