On Mon, Oct 15, 2012 at 01:20:49PM +0200, Milan Babuskov wrote: > On Mon, Oct 15, 2012 at 12:18 PM, Willy Tarreau <[email protected]> wrote: > > You should try to add "option http-pretend-keep-alive" > > Together with http-server-close or standalone? I assume the latter, > but need to be sure.
No, the former. http-server-close adds "Connection: close" to the request. With pretend-keep-alive, it does not, so the server sees the original request. > > Also, could you please send me a tcpdump > > capture of the connection from the client to haproxy and one from > > haproxy to the server ? > > I wish I could. It's a live production system. I have about 120GB of > websocket/xhr-polling traffic on that service daily, and only a small > fraction of clients with the problem. Main problem here is that I > cannot reproduce the problem myself as I don't have a Mac nor > iPhone/iPad, so I only rely on user reports which is about 20 per day. > Trying to find those is like searching for a needle in a haystack. OK I didn't know that it was that difficult and that little common. > AFAICT, there is no way to isolate Safari users when using tcpdump? When dealing with large captures, I use an hex editor to look for the strings I need, then locate the source port in the stream and filter on this. Granted this is not the most obvious method but it's efficient for me at least :-) > I'll try Windows version of Safari to see if I could reproduce the problem. Good idea. Willy
