acls and httpclose

From: Angelo Höngens <a.hongens#netmatch.nl>
Date: Wed, 21 Apr 2010 22:24:17 +0200

Hey, I read somewhere on the list that when you use keepalives, only the first request in the connection is matched to an acl, and then the other requests in the connection are not evaluated.

I noticed this behavior as well. As an experiment I set up a large config, where I select one out of 325 backends, based on one out of 8000 host headers. I noticed that only the first request in a connection is matched to a backend, and the rest follows to the same backend, even though the host header is different. With the httpclose option, everything works as it should.

My question is: is this behavior by design, or is this a work-in-progress?

I want to use haproxy for content switching on a large scale (lot of acls, lot of backends), but with httpclose on haproxy uses 25% cpu, without httpclose haproxy uses 5% cpu. So I'd rather not use httpclose if I don't have to..

-- 


With kind regards,


Angelo Höngens
systems administrator

MCSE on Windows 2003
MCSE on Windows 2000
MS Small Business Specialist
------------------------------------------
NetMatch
tourism internet software solutions

Ringbaan Oost 2b
5013 CA Tilburg

+31 (0)13 5811088
+31 (0)13 5821239
A.Hongens#netmatch.nl www.netmatch.nl ------------------------------------------
Received on 2010/04/21 22:24

This archive was generated by hypermail 2.2.0 : 2010/04/21 22:30 CEST