> I think you can use url rewriting, and that won't put the jsessionid on it.
It's sort of the other way around :-). The "jsessionid" parameter is the *result* of performing URL rewriting. If your browser client is using cookies, this will only show on the first request for a session - the container has to send the session id both ways (cookie and rewriting) the first time, because it doesn't know whether or not the client has cookies enabled. When the second request comes in with a cookie, the container notices and stops bothering to rewrite. > Since the jsessionid is what is used for session tracking, you want to look at > changing how session tracking is done. The Struts tags always do the URL rewriting calls for you, so that sessions "just work." If you never want to see the rewritten URLs, most containers have a way to configure disabling this feature -- but, if you do, sessions will only work for clients that have cookies turned on. Craig > > > > --------------------------------------------------------------------- > 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]
