hy;
just a stupid suggestions:
If the servletengine adds the sessionid "magically" to the
redirect URL, maybe there is also a configuration param, that
controls this behaviour of the servlet engine?
By the way, which servlet engine are you using?
regards, Hussayn
Carsten Ziegeler wrote:
Volker Schneider wrote:
Hi Carsten,
but if I set the "session" attribute to "false" in map:redirect-to, then I
would think that I can force cocoon to avoid adding the session
id this way.
No, setting this attribute to "true" means, that a new session is created
if not already available. Setting to "false" is the default and does not
touch the session, which means if a session is existent it's still there,
if not then no new session is created.
In my opinion this must be a bug.
As a pointed out, I *guess* (it's only a guess because I saw this several
times) it's a bug in the servlet engine.
However, as a workaround, it might be possible to first terminate the
existing session via an action and then do the redirect (if the flow
of the web application allows this).
Carsten
Carsten Ziegeler
Open Source Group, S&N AG
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
--
Dr. Hussayn Dabbous
SAXESS Software Design GmbH
Neuenhöfer Allee 125
50935 Köln
Telefon: +49-221-56011-0
Fax: +49-221-56011-20
E-Mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
