[Seaside] Multiple cookies in the HTTP headers

Boris Popov boris at deepcovelabs.com
Tue Oct 10 19:06:54 UTC 2006

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


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.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: WAResponse-addCookie.st
Type: application/octet-stream
Size: 451 bytes
Desc: WAResponse-addCookie.st
Url : http://lists.squeakfoundation.org/pipermail/seaside/attachments/20061010/62a74025/WAResponse-addCookie.obj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Root.Smalltalk.Seaside.WACookie-comparing.st
Type: application/octet-stream
Size: 632 bytes
Desc: Root.Smalltalk.Seaside.WACookie-comparing.st
Url : http://lists.squeakfoundation.org/pipermail/seaside/attachments/20061010/62a74025/Root.Smalltalk.Seaside.WACookie-comparing.obj

More information about the Seaside mailing list