Hi, Le vendredi 9 avril 2010 20:21:24, Willy Tarreau a écrit : > > With 1.3.22 and .24 I just get the "manage_server_side_cookies". When I > > constantly deny the cookie, > > the requests are round robbed, while with 1.4.4 they are sticky from the > > first request on, because > > the url appsession lookup in the url is working. > > Could you please also include a dump of the exchange between the client and > haproxy (or even an output of "haproxy -d") ? It is possible that something > appears mangled and that we're not thinking about it. > > > Will this be fixed in 1.3.x or do you suggest to upgrade to 1.4? > > No, there is no reason to upgrade for something that ought to work. 1.3 is > still maintained, so if it is supposed to work and it doesn't, it's a bug > and it needs to be fixed. If the fix is too dangerous, we may reconsider > this but right now this has not been qualified yet. However, you can use > 1.4 as a workaround (or maybe you plan to upgrade for other reasons).
Well, no this is not really a bug. HAProxy 1.3.x only parses the path parameters, behind a semicolon (and only the first one), like http://test/cookie.php;jsessionid=xxxxx?querystring The only "bug" is that the documentation says it checks the query string, which is not true. That's why I added a mode to appsession in one of the 1.4.x patch, which allows to choose between path parameters and the query string. http://haproxy.1wt.eu/git?p=haproxy-1.4.git;a=commit;h=b21570ae0f5024b86b72762a519972fbce5b307e Now, what I don't understand : why your JSESSIONID parameter is in the query string ? which server do you use to allow that ? -- Cyril Bonté
