[issue1564508] RFC 2965 BaseCookie does not support "$Port"

Martin Panter added the comment: The original report comes from . Anders was trying to parse a HTTP request Cookie field, something like: BaseCookie('sessionid=a2be2e7debe71af8d88d350c4d14d768;$Path=/;$Domain=192.168.0.2;$Port="8000"') The problem i

[issue1564508] RFC 2965 BaseCookie does not support "$Port"

Changes by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mai

[issue1564508] RFC 2965 BaseCookie does not support "$Port"

Mark Lawrence added the comment: This won't go anywhere unless someone provides a patch. -- nosy: +BreamoreBoy versions: +Python 3.2 ___ Python tracker ___ ___

[issue1564508] RFC 2965 BaseCookie does not support "$Port"

Ben Anhalt added the comment: Grrr, the link in my last comment should have been http://www.nabble.com/System.Net.CookieContainer-adding-inappropriate-%24Port-attribute-to-cookies--td23752882ef1367.html Yuck. -- ___ Python tracker

[issue1564508] RFC 2965 BaseCookie does not support "$Port"

Ben Anhalt added the comment: Actually, I was just bit by this. In fact, RFC 2965 prohibits clients from sending $Port if the port attribute was not included in the Set-Cookie header. But, it turns out that the mono System.Net library (at least) will add the attribute any time the URI includes

[issue1564508] RFC 2965 BaseCookie does not support "$Port"

Daniel Diniz added the comment: Does anybody else need this one or should it be closed? -- nosy: +ajaksu2 title: BaseCookie does not support "$Port" -> RFC 2965 BaseCookie does not support "$Port" type: -> feature request ___ Python tracker