BTW, I am working on something like this.
Won't commit on any deadlines either.
___
varnish-dev mailing list
varnish-dev@projects.linpro.no
http://projects.linpro.no/mailman/listinfo/varnish-dev
In message <4b027ecb.9050...@qbranch.se>, Robert Olsson writes:
>Hello!
>Is there any plan to support sticky sessions in varnish?
Plans ? yes.
Deadlines ? No.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello!
Is there any plan to support sticky sessions in varnish?
Some of the sessions will be a cookie-based logins and I need them to use the
same backend (in varnish point of view) during the whole session.
First when the backend server stop answering
ao...@mosso.com writes:
> Hash by client source port number and you'll get a nice even
> distribution.
Won't work, Opera opens multiple parallel connections to each server
(IIRC: 4 by default, configurable up to 16)
DES
--
Dag-Erling Smørgrav - d...@des.no
___
Hash by client source port number and you'll get a nice even distribution.
Adrian
Sent via BlackBerry by AT&T
-Original Message-
From: "Albert Lash"
Date: Fri, 20 Nov 2009 13:24:54
To: Artur Bergman
Cc: varnish-dev@projects.linpro.no; Robert
Olsson
Subject: Re:
Use of a cookie would definitely work, and there are probably a bunch of
other simpler methods too. One example - I would add client ip addresses
to the hash and select a backend based upon it, randomizing previously
unknown ip addresses. Depending on where the clients are, the load balance
might b
set a cookie and direct on that cookie?
On Nov 20, 2009, at 1:21 AM, Robert Olsson wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hello!
> Is there any plan to support sticky sessions in varnish?
> Some of the sessions will be a cookie-based logins and I need them
> to use the
> s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello!
Is there any plan to support sticky sessions in varnish?
Some of the sessions will be a cookie-based logins and I need them to use the
same backend (in varnish point of view) during the whole session.
First when the backend server stop answering
