Compensation for #6527

> On Thu, 2008-01-24 at 14:38 +0100, Lukas Renggli wrote:
>>> I thought the bug report explained this behaviour.
>> It looks like you are using a cookie-session, but your have disabled
>> cookies in your web-browser. There are indeed some bugs related to
>> cookies and updateUrl:.
>>
>
> No, useSessionCookie is false and my firefox accepts cookies
> until they expire. I'm using seaside 2.7. I hope this is ok.
>
> I parse the url in initialRequest: and I want the URL to be
> shown in the browser exactly as it was entered in the browser.
> I understand the bug report that in general this is the case
> but the first query which tries to find out about cookies
> intercepts this. Every further request shows the URL I tweak
> in updateUrl:. So it is neither the Url taken from the user
> nor the Url taken from updateUrl:
>
> thanks,
>
> Norbert
>
> _______________________________________________
> seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>

> A while back (when I originally reported the bug) the problem occurred
> because of the extra redirect taking place when useSessionCookie returns
> true.
>
> >From memory, the redirects should be:
>
> The initial request (what the user types) - /foo/bar
> The request to check if the cookie is available - /?_k=12345&_c
> The final request - /foo/bar/?_k=12346&_c
>
> However, the final request does not change the url from /?_k=12345&_c.
>
> Firefox has accept cookies enabled.
>

> > Yes, is the desired behaviour of having the /foo/bar Url achievable
> > or not? Lukas didn't answer and I'm quite unsure about what was the
> > outcome of this thread :)
>
> Did you try what I suggested?
>
> initialRequest: aRequest
>      super initialRequest: aRequest.
>      self session redirect
>
> I guess that should work, no?
>