[Zope-dev] More robust cookie handling
Hi during some testing I did I stumbled over this problem. When a client which is accessing a page on a Zope server sends a _ZopeId with other spelling (e.g. _ZOPEID). Zope does not accept the cookie and (obviously) sends a new value in the answer. According to RFC 2965 and RFC 2109 (defines the Set-Cookie header but is obsolete by RFC 2965) the NAME part of a name-value pair is treated case-insensitive. I'm not sure if this is a issue worth bothering as all user-agents seem to leave the NAME part intact (except my self-written test-suite ;). Changing the behaviour to ignore the case of the name would make it somewhat more robust. If you think it is worth bothering I will open an Issue in the Collector. regards Stefan ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] More robust cookie handling
--On Mittwoch, 30. März 2005 17:06 Uhr +0200 S.Aeschbacher [EMAIL PROTECTED] wrote: Hi during some testing I did I stumbled over this problem. When a client which is accessing a page on a Zope server sends a _ZopeId with other spelling (e.g. _ZOPEID). Zope does not accept the cookie and (obviously) sends a new value in the answer. It this a real-world problem? I'm not sure if this is a issue worth bothering as all user-agents seem to leave the NAME part intact (except my self-written test-suite ;). Changing the behaviour to ignore the case of the name would make it somewhat more robust. Are there any browsers that change the name? If not, I don't care :-) -aj pgpyvkiTeW9Gf.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
