Hi Randy, with the information you sent, I finally managed to reproduce the issue here. At first glance it seems to happen when "expect: 100-continue" is used. I can also confirm that using "option http-no-delay" works around the issue. I am investigating to get a fix ASAP, as for me this looks like a bug in haproxy. Both 1.4.19 and 1.5-dev exhibit the same behaviour.
Regards, Willy
