The jsessionid is managed by the servlet container. My understanding is
that it detects whether the use supports cookies and if so uses a
cookie. Otherwise it is sent as you see here. I know of no way to change
this. What you probably need is a bit of javascript on the page to
detect whether cookies are enabled and then cause an error message in
the browser. You should do this before the session is even created.
Tobia Conforto wrote:
Let me explain the problem a bit more.
I'm still curious about the issue, although I've found a workaround.
According to the docs Cocoon will not rewrite URLs, unless you use the
encodeURL transformer or call the equivalent flowscript function.
What I'm seeing is that the Location header of a client-side redirect
gets rewritten somewhere between my flowscript call and the network.
I call:
cocoon.redirectTo('test')
And on the wire I see:
Location: http://my.server/test;jsessionid=xxxxxxxxxx
Who is rewriting the URL? Cocoon or Jetty? How can I disable it?
The workaround I've found is calling redirectTo like this:
cocoon.redirectTo('http://my.server/test', true)
With both a full URL as the first parameter and true as the second one,
the Location URL doesn't get rewritten.
Tobia
---------------------------------------------------------------------
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]