Zope doesn't handle multiple cookies with the same id

[dom_1]

Zope stores cookies keyed by their id, but browsers can present two cookies with the same id, set at different paths:

from http://www.ietf.org/rfc/rfc2109.txt:

"If multiple cookies satisfy the criteria above, they are ordered in
   the Cookie header such that those with more specific Path attributes
   precede those with less specific. Ordering with respect to other
   attributes (e.g., Domain) is unspecified."

The first (i.e. most specific and therefore most relevant) cookie will be unavailable from Zope. This is a real problem when using cookie paths to manage multiple sessions with differing data depending on the locale.

[dom_1 (dom-1)]

> The first (i.e. most specific and therefore most relevant) cookie will be
> unavailable from Zope. This is a real problem when using cookie paths to
> manage multiple sessions with differing data depending on the locale.

... that should probably read "...only the last (and therefore least relevant) cookie will be available from Zope" (!)

[dom_1 (dom-1)]

> = Comment - Entry #2 by dom_1 on Aug 1, 2007 12:03 am
>
> > The first (i.e. most specific and therefore most relevant) cookie will be
> > unavailable from Zope.
>
> ... that should probably read "...only the last (and therefore least
> relevant) cookie will be available from Zope" (!)

Sorry for the noise here - the above statements were incorrect - Zope does return the most relevant cookie, just not all cookies holding the same id. Consequently, this bug is far less problematic than first thought.

[Andreas Jung (ajung)]

Changes: submitter email, edited transcript, importance (medium => low)

[Colin Watson (cjwatson)]

The zope2 project on Launchpad has been archived at the request of the Zope developers (see https://answers.launchpad.net/launchpad/+question/683589 and https://answers.launchpad.net/launchpad/+question/685285). If this bug is still relevant, please refile it at https://github.com/zopefoundation/zope2.