[Seaside] [2.6b1-mb.131] URL changes?

Boris Popov boris at deepcovelabs.com
Tue Feb 13 17:17:42 UTC 2007

Michel, that does the trick thanks!

Lukas, seems like my problems had nothing to do with the trailing slash,
so I'd like to withdraw my objection as it makes no difference as far as
I can tell otherwise for what we do here,



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.

-----Original Message-----
From: seaside-bounces at lists.squeakfoundation.org
[mailto:seaside-bounces at lists.squeakfoundation.org] On Behalf Of Boris
Sent: Tuesday, February 13, 2007 7:40 AM
To: seaside at lists.squeakfoundation.org
Subject: Re: [Seaside] [2.6b1-mb.131] URL changes?

Awesome thanks, I shall check it out,


(Sent from a BlackBerry)

----- Original Message -----
From: seaside-bounces at lists.squeakfoundation.org
<seaside-bounces at lists.squeakfoundation.org>
To: The Squeak Enterprise Aubergines Server - general discussion.
<seaside at lists.squeakfoundation.org>
Sent: Tue Feb 13 07:37:57 2007
Subject: RE: [Seaside] [2.6b1-mb.131] URL changes?

Hi again,

The fix is in Seaside-Swazoo (2.6b1.131.1,mbany) and also in
Seaside-WebToolKit (2.6b1.131.1,mbany).
The fix is making sure that path=/ is set in the set-cookie header, like
in Squeak.
Apparently this is needed for the session cookie to be properly deleted.

I also created Seaside (2.6b1.131.1,mbany) that includes your WAUrl
safeguard fix.
therefore if you reload the Seaside bundles using
you should get everything.

(Sent from a PC)

        Oh okay, it may be VisualWorks specific then, I shall take
another look today. If anyone else is on VisualWorks, I wouldn't mind
confirming the issue.
        Hi Boris,
        Like Lukas, I could not repeat this with Squeak.
        But, I was able to reproduce with VW.
        It looks as if the Seaside session cookie is not
        deleted when a new session is started with session
        cookies enabled. It seems to be related to the path=
        parameter in the set-cookie header. So the bug is most
        probably elsewhere, not in the pathString method.
        I'm working on a possible fix.
        Thanks for your patience,


More information about the Seaside mailing list