On Mon, Mar 05, 2012 at 07:04:44AM +0100, Baptiste wrote: > Hi, > > I would have suggest playing with the "option tcp-smart-connect" or > "no option tcp-smart-connect" on the backend side, since the response > time you observe is on the server side.
The smart-connect should not affect response time at all because it saves one packet before another one in the same direction (client to server). There is another trick which can be used : "option http-no-delay" in either the frontend or the backend. If it solves the issue, normally it means there is a bug in the application (eg: wrong advertised content-length or missing last chunk). > As Willy mentionned, it would be interesting to get a capture of a > single curl request passing through the haproxy box, using the "-i > any" flag as well to get incoming and outgoing traffic. Yes, this would definitely help. Willy
