Author maxy@debian.org
Recipients B. Kyven, demian.brecht, maxy@debian.org
Date 2013-02-27.08:27:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1361953658.04.0.661576304457.issue17251@psf.upfronthosting.co.za>
In-reply-to
Content
I've deleted my previous patch, as I found the code working as intended.

The domain_specified signals whether the domain stores came from a Domain: tag inside a Set-Cookie request or is taken from the hostname of the request.

The rfc2965 dictates that a value taken from a Domain: tag should be
prepended with a "." if the values doesn't include it. Once stored in a LWPCookieJar the same logic is used to signal if the domain_specified is true or false. Thus the observed behaviour.

The LWP-Cookies-2.0 format is an extension to the perl format, that seeks compatibility adding some features.

About the domain matching, the rfc2965 documents this. I think the perl comment is an example for a.b.c.net, so that matchs with .b.c.net but not with b.c.net.
History
Date User Action Args
2013-02-27 08:27:38maxy@debian.orgsetrecipients: + maxy@debian.org, demian.brecht, B. Kyven
2013-02-27 08:27:38maxy@debian.orgsetmessageid: <1361953658.04.0.661576304457.issue17251@psf.upfronthosting.co.za>
2013-02-27 08:27:38maxy@debian.orglinkissue17251 messages
2013-02-27 08:27:37maxy@debian.orgcreate