It will work as you said, if you have not enabled cookie persistence.
(cookie line in your backend conf).

by default, without http-server-close option, HAProxy will "tunnel"
requests and responses.
It will be able to analyze only the first request, taking rooting
decision, then all following requests will have to follow the same
route path.

Using http-server-close, HAProxy is able to take routing decision for
the HTTP connection, so, objects can be downloaded from any server in
a farm.

When you enable cookie persistence, then HAProxy will bypass the
balance algorythm, since it already knows how to route the request.


On Tue, Nov 22, 2011 at 6:17 AM, wsq003 <wsq...@sina.com> wrote:
> Hi,
> In my condition, I set the http-server-close option for client-side
> keepalive.  (You know this will save the time of establish connections)
> My question is will haproxy re-assign backend server for every HTTP request
> in this connection? I also configure 'balance uri' and
> 'hash-type consistent'.
> e.g. I hope /a/b.jpg and /c/d.jpg be assigned to different backend server
> based on consistent-hashing, even when they are in a same
> client-side connection.
> Thanks in advance.

Reply via email to