Hi again,
Le 30/04/2014 00:04, Cyril Bonté a écrit :
Hi,
Sorry but it's difficult to understand your test case.
OK, this time I think I could understand your issue and reproduce it.
The minimal setup I've used :
defaults
mode http
listen test :80
balance url_param q
hash-type consistent
server s demo.1wt.eu:80
This was introduced between 1.5-dev22 and 1.5-dev23 with this commit :
BUG/MEDIUM: http: don't start to forward request data before the connect
http://haproxy.1wt.eu/git?p=haproxy.git;a=commit;h=80a92c02f478dc1b836e0c97c891875437fc54da
Moreover, during my tests haproxy took 100% cpu after the second request
was sent to the persistent connection.
It's late now so I can't analyze it more precisely tonight but I think
it can be easily fixed now.
--
Cyril Bonté
