Isn't that for URL rewritting only? When you use a session through cookie, I think you can name it anything you want.
-----Original Message----- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED] Sent: July 29, 2003 10:12 AM To: Struts Users Mailing List; Struts Users Mailing List Subject: Re: [OT] Is "jsessionid" specific to Tomcat or generic to all web containers? On Tue, 29 Jul 2003, Matthias Bauer wrote: > Date: Tue, 29 Jul 2003 11:01:32 +0200 > From: Matthias Bauer <[EMAIL PROTECTED]> > Reply-To: Struts Users Mailing List <[EMAIL PROTECTED]>, > Struts Users Mailing List <[EMAIL PROTECTED]> > To: Struts Users Mailing List <[EMAIL PROTECTED]> > Subject: Re: [OT] Is "jsessionid" specific to Tomcat or generic to all > web containers? > > Craig, > > all this sentence says is that the session id must be encoded as a path > parameter. But it does not say anything about the name, the implementing > server is supposed to use. Is there some other place in the spec where > it says that the parameter must be called "jsessionid"? If not, I would > say the server implementation is free to choose any name. Am I > overlooking something? I don't know about you, but I find the following sentence in 7.1.3 The name of the parameter must be jsessionid. to be pretty clear :-). It's just before the example. 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]
