Re: option redir and latest snapshot

On Thu, Feb 14, 2008 at 08:34:40PM +0100, Willy Tarreau wrote:
> On Thu, Feb 14, 2008 at 03:48:29PM +0100, florian iragne wrote:
> > Once properly configured, the redirection works perfectly well. The only
> > problem is that i must deactivate the server checking, otherwise haproxy
> > declares all server down (when they have redir option) or alternatively
> > up/down (when no redir is specified).
>
> I don't see how that may happen, especially the no-redir case. I'll look at
> this when I'm back home this evening.

Well, I've just checked and not only I do not see anything affecting the check code, but local tests here show that it works as usual for me, both with or without the redir option.

> > Checking the access log of the webservers, i can see the "HEAD /
> > HTTP/1.1" 200 from haproxy (this is the check string i must send to
> > nginx to enable the proper response for haproxy).

I'm just wondering: if you're using "HEAD /" on a static server, it's generally not a good idea as this will require the server to perform directory listings which may be CPU and IO intensive, and require much time to complete under load. On static servers, it's usually recommended to check /alive and have such a file there.

For your convenience if you want to retry the fixed version, I've pushed it here :

   http://haproxy.1wt.eu/download/1.3/src/Beta/haproxy-1.3.14-51.tar.gz

Best regards,
Willy Received on 2008/02/14 22:02