This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author jerry.seutter
Recipients BM, jerry.seutter
Date 2008-02-26.09:46:34
SpamBayes Score 0.013815993
Marked as misclassified No
Message-id <1204019196.73.0.947240519282.issue2193@psf.upfronthosting.co.za>
In-reply-to
Content
Hm.  Your bug doesn't agree with my interpretation of the RFC's.

RFC2109 section 4.1 states that the the cookie name (attr) is of type
"token", which in RFC2068 section 2.2 is defined as any chars excluding
control characters and special characters.  RFC2068 lists special
characters as 
tspecials      = "(" | ")" | "<" | ">" | "@"
                         | "," | ";" | ":" | "\" | <">
                         | "/" | "[" | "]" | "?" | "="
                         | "{" | "}" | SP | HT

... so the ":" in a cookie name should not be allowed.

RFC2965 and RFC2616 (which obsolete the above RFC's) state the same thing.

Either I'm wrong or the other languages you cite are differing from the
RFC.  Do you have any idea why they might be doing that?
History
Date User Action Args
2008-02-26 09:46:37jerry.seuttersetspambayes_score: 0.013816 -> 0.013815993
recipients: + jerry.seutter, BM
2008-02-26 09:46:36jerry.seuttersetspambayes_score: 0.013816 -> 0.013816
messageid: <1204019196.73.0.947240519282.issue2193@psf.upfronthosting.co.za>
2008-02-26 09:46:35jerry.seutterlinkissue2193 messages
2008-02-26 09:46:35jerry.seuttercreate