Am Freitag, 23. Januar 2004 19:59 schrieb Michael E. Allen:
Where would I put that?
Already tried putting it in the <%@ page [..] %> on top of
your JSP pages? :-) As Struts tends to create a session implicitly,
such as for storing the default locale settings etc, doing so in the end would show no real effect anyway (provided that
you're not doing direct JSP calls, but wrap them into a standard Struts forward action at least, which is definitely recommendable).
Considering the URL rewriting issue: just yesterday I wrote about enforcing Cookies (for certain parts of the application that won't work otherwise, among these those invoking external systems written in other languages inside a session-wide transaction), so I better refer to that post here. Normally, supporting URL rewriting is definitely a good thing, and you shouldn't suppress this fine mechanism unless you have to. If you have to, still, you can always say session.invalidate() and do a normal forward, in a custom Action.
HTH, -- Chris.
Anyway... I ended up doing a double redirect... the first to get the cookie set and the second to get the URL without the "?JSESSION=xxx" stuff appended.
Eric Bariaux wrote:
What about session=false on your jsp page directive? Would this help? Eric.
-----Original Message----- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Michael E. Allen Sent: Thursday, January 22, 2004 10:37 PM To: [EMAIL PROTECTED] Subject: Re: Help URL Rewriting
Ted Husted wrote:
The container can't be sure that any given client supports cookies,
so
it will always use URL rewriting on the first request.
Is there any way to shut that off? From and Action I am returning an ActionForward from the execute that maps to an jnlp file. The "?jsessionid=090280243" at the end is messing up starting java web start. I can tell me users to hit refresh once and it will go away... but there should be a better way!
I am not using jsp... the page I want to forward to is a jnlp file (java web start), so there is no jsp directive in that file. I am not a jsp programmer, so I thought perhaps there was a configuration file somewhere.
In any case, neither setting session=false nor calling session.invalidate() will do what I want; because I *do*, in fact, want there to be a session. I just don't want the JSESSIONID appended to the url on the first call.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
