[Seaside] Multiple cookies in the HTTP headers
philippe.marschall at gmail.com
Thu Oct 12 06:42:08 UTC 2006
I had a look at the patches and have a question:
For equality you take the key, value, expiry and path into account.
Does this make sense (semantically)? Wouldn't it be better to just use
the key and path? Or just the key? I mean it's called key for a
2006/10/10, Boris Popov <boris at deepcovelabs.com>:
> Attached file-outs (VisualWorks) include a fix to multiple equivalent
> cookies being added to the response. Specifically, the initial request
> would go through WASession>>start: and subsequently
> WASession>>redirectWithCookies: which would add a session cookie to the
> response, but WASession>>respond: would also add the same cookie to the
> same response. While the correct fix might be to not do a
> redirectWithCookies on session start when using cookies, the attached
> fixes ensure that adding equivalent cookie to the response will never
> result in it being listed there multiple times.
> DeepCove Labs Ltd.
> 4th floor 595 Howe Street
> Vancouver, Canada V6C 2T5
> boris at deepcovelabs.com
> CONFIDENTIALITY NOTICE
> This email is intended only for the persons named in the message
> header. Unless otherwise indicated, it contains information that is
> private and confidential. If you have received it in error, please
> notify the sender and delete the entire message including any
> Thank you.
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
More information about the Seaside