RE: Track headers with tcp-request in listen only work with if HTTP

Hello, I reply to myself. I think that is because the tcp-request need a condition for doing the track. Tranks, Ricardo F From: ri...@hotmail.com To: haproxy@formilux.org Subject: Track headers with tcp-request in listen only work with if HTTP

RE: How to redispatch a request after queue timeout

Hi Sachin, We want to maintain stickiness to a backed server based on host header  so balance hdr(host) works pretty well for us, however as soon at the backend hits max connection, requests pile up in the queue eventually timeout with a 503 and –sQ in the logs. I don't think balance

Re: How to redispatch a request after queue timeout

Thanks Lukas. Yes, I was hoping to workaround by setting a smaller maxqueue limit and queue timeout. So what other options do we have, I need to: 1. Send all requests for a host (mytest.mydomain.com) to one backend as long as it can serve. 2. If the backend is swamped, it should go to any other

Issue with tcp-request content and keep alive

Hello, I have an issue when trying to track a connection based on a header, with tcp-request, and with keep alive enable in a listen section. Over the haproxy i have a cdn, which pass the ip of the client at the beginning of the X-Forwarded-For header. All the requests are pass through this

Re: Debugging Backendforwarding and UP status

Baptiste, at first, sorry, I meant to say hi, but I had a very long night and it seems I have missed it. About the html. Thunderbird has a default html and txt message setting by default, normaly I change that, but as I said, I had a long night. The next time I'll remember that. Concerning

Bénéficier d'un catalogue interactif pour vos produits et services

CRÉATION DE CATALOGUES PAPIER ET INTERACTIF B.T.I est une agence de communication globale dont l'une des compétences est la création, la réalisation ou la mise à jour de catalogues papier et interactif de vente .Le studio graphique de l'agence intègre toutes les compétences pôur la

Re: junk at end of syslog packets in 1.5dev19

On Thu, Aug 29, 2013 at 10:50:09PM +0200, Lukas Tribus wrote: The behavior also depends on the syslog facility; I used syslog in my tests. With the current git tree I see the following behavior: ntp and local7: syslog ends with \n -- correct behavior! ftp and user: syslog ends with \n + 2

RE: junk at end of syslog packets in 1.5dev19

Hello Lukas, Thanks for your analyze, the bug was indeed caused by the number of digits in the facility. Here's a patch with the real size to send :) Thanks, I confirm it fixes the problem. Regards, Lukas