haproxy not logging correctly or I am misunderstanding something?

2011-08-26 Thread Dean Hiller
Not sure if this is my confusion or if there is something wrong. Version 1.3.22-1 of haproxy according to apt-cache pkginfo haproxy. The HAProxy log was(note the 10.0.3.12 and 200 success) Aug 26 17:18:58 localhost haproxy[990]: 10.0.3.12:42281[26/Aug/2011:17:18:43.503] appli1-rewrite

Re: haproxy not logging correctly or I am misunderstanding something?

2011-08-26 Thread Bryan Talbot
I think you're mixing up your client IP and server IP addresses. The 10.0.3.12:42281 is the source IP:PORT for the TCP connection making the request (the client). The request was serviced by the server named ip_10_0_2_14 which I assume has an IP address of 10.0.2.14. -Bryan On Fri, Aug 26,

How to test keep-alive is working?

2011-08-26 Thread bradford
How do I test that keep-alive is working? I've added option http-server-close to the frontend and do not see a connection header in the http response. I use to see connectino: closed when I had httpclose enabled, but don't see connection: keep-alive or anything similar. So, how do I test it's

Re: How to test keep-alive is working?

2011-08-26 Thread Bryan Talbot
You could use something as simple as curl to see if the connection is left in-tact. $ curl -I -v www.example.com If keep-alive is working, curl will include a verbose message like this: * Connection #0 to host www.example.com left intact and then close the connection since it has no pending

Re: How to test keep-alive is working?

2011-08-26 Thread Baptiste
Hi, In HTTP 1.1, Keep alive is the default mode and does not require any header. On the other hand, in HTTP 1.0, there is no keepalive by default, that's why browser and web servers had to anounce it. More information available here: