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-27.19:20:20
SpamBayes Score 0.099435315
Marked as misclassified No
Message-id <1204140023.63.0.393808520076.issue2193@psf.upfronthosting.co.za>
In-reply-to
Content
Heh, I think I should not have gotten involved in this bug. :)  I have a
few comments:

In response to 2.: David M. Kristol in that article is referring to the
original Netscape cookie implementation which is somewhat different from
what is set out in the RFC's.   Now I understand where the difference is.

In response to 6: Yes, I was referring to the NAME part of NAME=VALUE...


So it looks to me like the Python code implements the specification as
set out in the RFC.  I agree with you that there are multiple
implementations (Java and Perl) in wide use that allow behavior not set
out in the RFC.  The question is, do we want to stick the bahavior in
the RFC, or accomodate existing implementations?  My opinion:  I agree
with you.

Can some Python regulars comment on Python's policy in situations like this?

I can throw together a patch if this change would likely be accepted.
History
Date User Action Args
2008-02-27 19:20:24jerry.seuttersetspambayes_score: 0.0994353 -> 0.099435315
recipients: + jerry.seutter, BM
2008-02-27 19:20:23jerry.seuttersetspambayes_score: 0.0994353 -> 0.0994353
messageid: <1204140023.63.0.393808520076.issue2193@psf.upfronthosting.co.za>
2008-02-27 19:20:21jerry.seutterlinkissue2193 messages
2008-02-27 19:20:20jerry.seuttercreate