Re: redispatch does not work when httpchk fails?

On Tue, Jun 09, 2009 at 12:57:45PM +0200, Anders Nordby wrote:
> Hi,
>
> On Fri, Jun 05, 2009 at 06:45:05AM +0200, Willy Tarreau wrote:
> >> My problem is:
> >>
> >> 1) If I use JSESSIONID prefix, requests are sent to the two backends
> >> every second time each, meaning the session cookie is not respected.
> >> Why? How can I make the requests balanced separately per session? I
> >> tried roundrobin and lastconn.
> > you have not set "option httpclose", so haproxy adds the prefix to the
> > cookie in the first response, but when the server sends it again with
> > the second response in the same session, haproxy does not touch it so
> > it reaches the browser intact, without persistence information.
>
> That does not seem to help. JSESSIONID cookie is set (with path /) and
> sent for every request, but haproxy sends me from server to server for
> every request. I am using haproxy 1.3.18.

could you check on your browser that JSESSIONID has the server cookie as a prefix ?

Willy Received on 2009/06/09 13:57