On Thu, Dec 06, 2018 at 09:39:37AM +0000, Veiko Kukk wrote: > Hi, Willy > > On 2018-12-06 04:43, Willy Tarreau wrote: > > In the mean time it would be useful to see if adding > > "option http-pretend-keepalive" helps. This way we'll know if > > it's the server closing first or haproxy closing first which > > triggers this. And if it turns out that it fixes the issue for > > you, it could be a good temporary workaround. > > Indeed, adding "option http-pretend-keepalive" helps.
Great, thanks! So this means that the issue is with the close received form the server and not with the close sent to the server. This helps narrow the issue down. If you could take a network capture between haproxy and the server on a connection exhibiting the problem, it would be awesome. I'm saying this because I feel like there could be one behaviour explaining this : if we tell your server that we'd like it to close at the end of the transfer, and that for whatever reason it closes in a dirty manner (for example before reading the whole request in case of a POST), then it could cause it to send an RST and destroy the last few segments in flight that have not yet been received. This case is unusual so it's unlikely to be this but it could be an explanation and could justify why Christopher couldn't reproduce it last time. Thanks, Willy
