|
|
cURL Mailing List Monthly Index Single Mail
curl-tracker mailing list Archives
[ curl-Bugs-2544227 ] Old cookie not updated during FOLLOWLOCATION
From: SourceForge.net <noreply_at_sourceforge.net>
Date: Sun, 01 Feb 2009 18:46:10 +0000
Bugs item #2544227, was opened at 2009-01-29 01:10
Please note that this message will contain a full copy of the comment thread,
Initial Comment:
Server1 sets a cookie with value=Ax50
Server2 sets an unrelated cookie
Curl sends correct "value=Ax50" cookie
Server1 redirects to Server1 (again)
Both cookies end up in the cookiejar/file but the old one is at the top and still used.
It would take time to configure a server or two to set cookies during redirects so I haven't bothered to find the most simple case of this occurring. It may be a simple cookie overwrite problem. Hopefully someone can experiment or scan through the source.
This was with Windows PHP 5.
CURLOPT_FOLLOWLOCATION, 1
----------------------------------------------------------------------
>Comment By: Daniel Stenberg (bagder)
Message:
B) If this truly is something bad I would need an exact description,
----------------------------------------------------------------------
Comment By: actuator (actuator)
Message:
Since this is in the Netscape spec but behaves differently to browsers,
I could possibly patch the source myself but I haven't been able to work
----------------------------------------------------------------------
Comment By: Daniel Stenberg (bagder)
Message:
And about the path, the good old netscape spec says this about it:
"If the path is not specified, it as assumed to be the same path as the
----------------------------------------------------------------------
Comment By: actuator (actuator)
Message:
----------------------------------------------------------------------
Comment By: actuator (actuator)
Message:
Set-Cookie:
but in cookiefile.txt:
# Netscape HTTP Cookie File
www.server1.com FALSE /path1/ TRUE 4 some_value AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
.server2.com TRUE / FALSE 1 a 1234
www.server1.com FALSE /path1/long?pathwithvariables=in&pathwithvariables=in&pathwithvariables=in&pathwithvariables=in&pathwithvariables=in&pathwithvariables=in&pathwithvariables=in&pathwithvariables=in/ TRUE 4 some_value BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB
.server2.com TRUE / FALSE 3 d 1234
Hopefully that illustrates the problem without the actual data.
----------------------------------------------------------------------
You can respond by visiting:
These mail archives are generated by hypermail. |
Page updated November 12, 2010.
web site info