Thanks Craig & others... So that means for servlet spec 2.2 onwards, "jsessionid" in a url is a standard for url session encoding, along with the ";" and it position right after the path.
eg. http://www.dot.com;jsessionid=123?param1=value1¶m2=value2 Cool, your explaination is so much clearer. Thanks! Regards, Daniel -----Original Message----- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED] Sent: Monday, 28 July, 2003 11:41 PM To: Struts Users Mailing List; [EMAIL PROTECTED] Subject: Re: [OT] Is "jsessionid" specific to Tomcat or generic to all web containers? On Mon, 28 Jul 2003, David Graham wrote: > Date: Mon, 28 Jul 2003 06:37:49 -0700 (PDT) > From: David Graham <[EMAIL PROTECTED]> > Reply-To: Struts Users Mailing List <[EMAIL PROTECTED]>, > [EMAIL PROTECTED] > To: Struts Users Mailing List <[EMAIL PROTECTED]> > Subject: Re: [OT] Is "jsessionid" specific to Tomcat or generic to all > web containers? > > The JSESSIONID cookie is standard but a more interesting question is > whether the url rewriting format is standardized? I haven't been able to > confirm that http://blah.com;jsessionid=42789?qry=test&qry2=test2 is > standard. > The URL rewriting format is also standardized; in section 7.1.3 you will see the sentence: The session id must be encoded as a path parameter in the URL string. A "path parameter" is defined in the RFCs that define the formats of URLs. Among other things, that means it is separated by a semicolon (";") instead of a question mark or ampersand, and that path parameters come first. > David 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]
