From 877dad1e24876030a7dd8738648f0f0245b6331a Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Tue, 19 Jan 2010 23:19:59 +0000 Subject: - As was pointed out on the http-state mailing list, the order of cookies in a HTTP Cookie: header _needs_ to be sorted on the path length in the cases where two cookies using the same name are set more than once using (overlapping) paths. Realizing this, identically named cookies must be sorted correctly. But detecting only identically named cookies and take care of them individually is harder than just to blindly and unconditionally sort all cookies based on their path lengths. All major browsers also already do this, so this makes our behavior one step closer to them in the cookie area. Test case 8 was the only one that broke due to this change and I updated it accordingly. --- tests/data/test8 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'tests/data/test8') diff --git a/tests/data/test8 b/tests/data/test8 index 6131894fd..15e643b66 100644 --- a/tests/data/test8 +++ b/tests/data/test8 @@ -55,7 +55,7 @@ Set-Cookie: blexp=yesyes; domain=.0.0.1; domain=.0.0.1; expiry=totally bad; GET /we/want/8 HTTP/1.1 Host: %HOSTIP:%HTTPPORT Accept: */* -Cookie: blexp=yesyes; cookie=yes; partmatch=present; foobar=name +Cookie: cookie=yes; partmatch=present; foobar=name; blexp=yesyes -- cgit v1.2.3