Daniel Stenberg wrote:
>> libCurl internally handles that cookie as session cookies, because
>> the expires value <= 0 and sends it to the server next time (despite
>> it is expired !).
>
> That's indeed a true bug. I figure we should simply consider -1 dates
> as invalid (expired) unconditionally so only (co->expires== 0 ||
> co->expires> now) sends the cookie. Right?
I assume co->expires is set to 0 by libCurl to mark it as a session
cookie (cookie has no expires attribute set) ?
Your proposed solution sounds good.

> Thanks for your detailed report and research.
Thanks for that good library :-)

Best regards,

    Stefan
Received on 2008-09-06