> On Nov 16, 2007 12:34 AM, <jon_at_linertia.com> wrote:
>
>>
>> When I run the curl operation on the website of interest, i.e.
>>
>> curl -vc cookie "www.example.com"
>>
>> the verbose output http header gives me:
>>
>> Added cookie session=XXXX for domain example.net, path /, expire 0
>> < Set-Cookie: session=XXXX path=/; domain=.example.net
>> * Added cookie PHPSESSID=AAAA for domain www.example.net, path /, expire
>> 0
>> < Set-Cookie: PHPSESSID=AAAA; path=/
>> * Replaced cookie session=YYYY for domain example.net, path /, expire 0
>> <
>> Set-Cookie: session=YYYY path=/; domain=.example.net
>>
>> Question: WHY is it replacing my cookie XXXX with YYYY? I need my
>> cookie
>> to be XXXX for logging in to work.
>
>
> The Set-Cookie lines are all coming from the server. Curl is correctly
> updating its cookie collection because the server is telling it to.
>
> Ralph Mitchell
>

Ralph,

Yes, but in firefox, it's using cookie XXXX. That's why something is
weird. When I try to login using firefox it's using cookie XXXX while
curl is trying to use cookie YYYY, which is why it's not working
correctly.

Jon
Received on 2007-11-16