Nevermind, something was (is) creating spurious sessions where it shouldn't. It will take a while to figure out what misguided component or piece of flowscript is doing so.
In the meantime I have put this in a couple places to make sure there is no session before calling redirectTo(): if (cocoon.request.getSession(false)) cocoon.session.invalidate() Otherwise redirectTo, which ends up calling response.encodeRedirectURL() (in HttpEnvironment.java:138) will add ;jsessionid to the URL. Tobia --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
