Hi, You actually right. Tested with curl worked like a charm.
Thank you. On 29 January 2014 14:00, Willy Tarreau <[email protected]> wrote: > On Wed, Jan 29, 2014 at 01:49:39PM +0000, Thorvald Hallvardsson wrote: > > Hi Willy, > > > > I have kept F5 pressed for number of seconds. Then I checked the status > > page and saw which node was active in the traffic. The first one only had > > something in the rest had zeroes. I tried that from different browsers > even > > different PCs and it has always gone to the first node on the list :/. > > OK so that confirms my doubts. The browser has no particular reason for > closing a working connection when you reload, so what you observe is normal > and expected. > > > As soon as I fired up haproxy 1.5 with the same config keeping F5 pressed > > for number of second result in the load being spread across the backend > as > > every single one had some bytes transferred in and out and also status > page > > which tells which node you're connected to was displaying different > results > > every time I refreshed the page so... it's not the connection open. > > May reasons are possible, one of them is that when you switch from 1.4 to > 1.5, you caused some connection errors between the browser and haproxy and > the browser decided to break these connections upon reload. I suspect that > even if you switch back to 1.4 after that, it will continue to > load-balance. > > That said, using a single browser with a single connection is never > reliable > as a test, precisely for this reason. Just close your browser and reopen it > between page accesses, or better, use a common tool such as "ab" or > whatever > equivalent you find. Even curl is fine for such unit testing. > > Regards, > Willy > >
