[Seaside] path appendix to initial url once more

Philippe Marschall philippe.marschall at gmail.com
Wed Feb 27 20:38:07 UTC 2008

2008/2/27, Norbert Hartl <norbert at hartl.name>:
> Hi,
>  I know now why the appendix to my URLs are missing.
>  Lukas advised to try something like this:
>  initialRequest: aRequest
>    super initialRequest: aRequest.
>    self session redirect
>  But the redirect is the one which removes the appendix
>  from the URL. actionUrlForKey: in WASession resolves
>  to WAEntryPoint>>baseUrl.
>  As long as there isn't any redirect it works quite
>  good. In my case it is the check for cookies which does
>  the redirect. Removing the check makes it work.
>  So for me there are two options how to solve the problem:
>  - there is an appropriate way of checking cookies without
>   redirecting. But I fear this has to be a javascript one
>   instead, right?

Right, but even in this case you would have to know before the initial
request whether cookies are supported. You could build a proxy that
does this before the initial request hits the Seaside application. Or
a static html page that would contain JavaScript and "forward to

And finally an other option would be to add the cookie as well as the
_s parameter to the very first response. As soon as we have a session
cookie we can drop the _s parameter. Seaside does currently not
support this as this depends on the J2EE refactoring.


>  - I'm not too familiar with how seaside works exactly. The
>   WASession>>actionUrlForKey: is the method which is called
>   in both ways (cookie check and session redirect). Would it
>   be feasible to take the appendix there from the current-
>   Request and append it to url?
>  thanks in advance,
>  Norbert
>  _______________________________________________
>  seaside mailing list
>  seaside at lists.squeakfoundation.org
>  http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

More information about the seaside mailing list