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 onc
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 wrote:
> On Mon, Mar 19, 2012 at 09:48:31PM +0100, Baptiste wrote:
>> Hey,
>>
>> Here is a configuration samp
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 coo
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) if
On Mon, Mar 19, 2012 at 6:32 PM, Willy Tarreau 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 thin
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 as flash server farm. There is only one
> application server f
Hi Willy,
On Mon, Mar 19, 2012 at 9:56 AM, Willy Tarreau 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 cr
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 s
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 th
Hi Willy,
On Sat, Mar 17, 2012 at 8:58 AM, Willy Tarreau wrote:
> Hi Kamil,
>
> On Thu, Mar 15, 2012 at 10:17:21AM +0100, Kamil Gorlo wrote:
>> Hi guys,
>>
>> I want to use HAproxy as a LB to my HTTP API, but I want to balance
>> requests based on some route_id provided either in cookie or in URI
Hi Kamil,
On Thu, Mar 15, 2012 at 10:17:21AM +0100, Kamil Gorlo wrote:
> Hi guys,
>
> I want to use HAproxy as a LB to my HTTP API, but I want to balance
> requests based on some route_id provided either in cookie or in URI
> (flash apps cannot set headers in requests). It looks that only
> appse
Hi guys,
I want to use HAproxy as a LB to my HTTP API, but I want to balance
requests based on some route_id provided either in cookie or in URI
(flash apps cannot set headers in requests). It looks that only
appsession supports reading URI,. Is there any way to do this with
cookie option? Or how
12 matches
Mail list logo