Hi Malcolm, On Mon, Mar 08, 2010 at 07:02:06PM -0800, Malcolm Handley wrote: > I'm having a problem with an haproxy setup where not all of the requests are > getting logged (even in debug mode). Specifically, I have an ajax app that > periodically POSTs to the server to find out about changes. I know that > these requests are going to the proxy because if I kill the proxy the > requests start failing. However, these requests are not logged to syslog or > printed to the console when haproxy is run in debug mode. Nor are they shown > in the stats. But the requests *are* sent to my web server and the responses > are forwarded back to the client, just without the addition of the cookie to > indicate which server should receive the next request from this client. This > is happening with 1.3.23 and 1.4. > > I'm still scouring the docs and the code trying to figure out what would > cause this but any pointers would be great.
Normally this is what happens when haproxy runs in "tunnel" mode, which means it only sees the first request of each connection. This has been the default since the beginning. In 1.3, you could set "option httpclose" to break the keep-alive and have one request per connection. In 1.4, you also have "option http-server-close" which ensures that keep-alive is maintained on the client side. I suspect you have neither option in your configuration. Hoping this helps, Willy
