Hi,
Use haproxy 1.5-dev branch and stick tables. In your backend, just add the
few line below:
stick-table type string len 32 size 10K
stick store-response set-cookie(YOURCOOKIENAME)
stick on url_param(YOURPARAMNAME)
You could combine this with a few ACL to match either the Cookie
header or
Hi Kamil,
On Mon, Mar 19, 2012 at 09:02:25AM +0100, Kamil Gorlo wrote:
To use our API you need to create session on server. You call /signin
and then backend sets the session cookie - it's highly preferred (for
some crucial features to work) that from now on all requests should go
to the same
Hi Willy,
On Mon, Mar 19, 2012 at 9:56 AM, Willy Tarreau w...@1wt.eu wrote:
Hi Kamil,
On Mon, Mar 19, 2012 at 09:02:25AM +0100, Kamil Gorlo wrote:
To use our API you need to create session on server. You call /signin
and then backend sets the session cookie - it's highly preferred (for
some
On Mon, Mar 19, 2012 at 6:32 PM, Willy Tarreau w...@1wt.eu wrote:
Hi Kamil,
On Mon, Mar 19, 2012 at 11:59:51AM +0100, Kamil Gorlo wrote:
Cookies are passed in two ways only:
- as regular http cookies
- as parameters in query string when first option is impossible
There is no such thing
Maybe I have to ask this in the keepalived list.
I have 2 servers configured in debian with keepalived and haproxy.
Today I found that both servers are running.
Keepalived is assumed that this active-passive, but ..
When I stop a server, the other works perfectly!
I followed this manual:
Hey,
Here is a configuration sample which may work with latest HAProxy version:
stick-table type string len 32 size 10K
stick store-response set-cookie(sessionID)
stick store-response set-cookie(routeID)
sitck on cookie(sessionID) if { hdr_sub(Cookie) sessionID }
stick on cookie(routeID)
On Mon, Mar 19, 2012 at 09:48:31PM +0100, Baptiste wrote:
Hey,
Here is a configuration sample which may work with latest HAProxy version:
stick-table type string len 32 size 10K
stick store-response set-cookie(sessionID)
stick store-response set-cookie(routeID)
sitck on
Well, I considered the collision domain very very tight ;)
Now, it's easy to prefix the cookie with some values to avoid collisions.
cheers
On Mon, Mar 19, 2012 at 9:54 PM, Willy Tarreau w...@1wt.eu wrote:
On Mon, Mar 19, 2012 at 09:48:31PM +0100, Baptiste wrote:
Hey,
Here is a configuration
On Mon, Mar 19, 2012 at 10:18:34PM +0100, Baptiste wrote:
Well, I considered the collision domain very very tight ;)
It's not a good idea to rely on probability to hope to get a reliable
platform. On many sites, something which happens only once in one million
will cause a complain somewhere
The main stats page says ressources (French spelling) rather than
resources (English spelling).
One little patch attached (against v1.4.20).
Many thanks,
Adrian
diff -Naur haproxy-1.4.20.orig/doc/architecture.txt haproxy-1.4.20/doc/architecture.txt
--- haproxy-1.4.20.orig/doc/architecture.txt
10 matches
Mail list logo
