I had similar issues changing from an HTTPs login page to a normal
HTTP session for speed. I gave up in the end (for now.) I was using
Tomcat, and it kept randomly creating a new session when switching
back and forth.
But, I'd bet it's really your servlet container that's doing this,
not Tapestry.
Norman Franke
ASD, Inc.
On Dec 26, 2007, at 10:41 PM, Steven Woolley wrote:
I am having an issue where a new session is being created by a
plugin within a page that already has a session. I need to use
just one session for both the page and the plugin. I've tried
appending the jsessionid to all the requests made by the plugin,
but a new session is still created (and the session id from the url
is apparently ignored in favor of the cookie's new session ids).
Is there a way to work around this, either by forcing the url
sessionid to be used, or something else?
Thanks,
Steve
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
