RE: [OT] Is jsessionid specific to Tomcat or generic to all web containers?
I think Craig already said the parameter having to be called jsessionid is part of a spec... Regards, Daniel -Original Message- From: Matthias Bauer [mailto:[EMAIL PROTECTED] Sent: Tuesday, 29 July, 2003 5:02 PM To: Struts Users Mailing List 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? --- Matthias 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. - 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]
RE: [OT] Is jsessionid specific to Tomcat or generic to all web containers?
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]
RE: [OT] Is jsessionid specific to Tomcat or generic to all web containers?
Would you by any chance be forwarding to a static resource in the case where this fails, and a dynamic resource (or JSP page) when it succeeds? If so, then the default servlet would indeed be an issue. If the request successful, I am forwarding to a jsp page in my Tiles Request Processor. However, I forward to an custom html 500 page if an exception occurs. The path in my global-exceptions in struts-config.xml (see below) forwards to this page. global-exceptions exception key= scope=request type=java.lang.Exception path=/locator500.htm handler=com.ams.transactionlocator.uboc.struts.DefaultExceptionHandler/ /global-exceptions Any ideas? Brian Husted AMS, Outsourced Solutions Group 410-897-1602 (phone) 410-897-1163 (fax) www.ams.com This email message is intended only for use by the recipient(s), and may contain confidential and proprietary information of AMS, Inc. Any unauthorized use, disclosure, or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of this email message. Craig R. McClanahan To: Struts Users Mailing List [EMAIL PROTECTED] [EMAIL PROTECTED]cc: org Subject: RE: [OT] Is jsessionid specific to Tomcat or generic to all web containers? 07/29/2003 01:21 PM Please respond to Struts Users Mailing List On Tue, 29 Jul 2003, Yansheng Lin wrote: Date: Tue, 29 Jul 2003 10:48:02 -0600 From: Yansheng Lin [EMAIL PROTECTED] Reply-To: 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? Isn't that for URL rewritting only? Yes, the path parameter stuff is for URL rewriting only. When you use a session through cookie, I think you can name it anything you want. No ... you really might want to read the spec before making assumptions like this. It is specific on the name of the session id cookie (JSESSIONID) as well, in Section 7.1.1. http://java.sun.com/products/servlet/download.html The entire section on how sessions work in a standard servlet container is only five pages, plus the Javadocs on the HttpSession class :-). 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]
Re: [OT] Is jsessionid specific to Tomcat or generic to all web containers?
I think it was Tomcat-specific at one time, but I think it is in the Servlet spec now. -Max - Original Message - From: Daniel Joshua [EMAIL PROTECTED] To: 'Struts Users Mailing List' [EMAIL PROTECTED] Sent: Monday, July 28, 2003 3:47 AM Subject: [OT] Is jsessionid specific to Tomcat or generic to all web containers? Quick question. Is jsessionid specific to Tomcat or generic to all web containers? Regards, Daniel - 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]
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=testqry2=test2 is standard. David --- Andrew Geery [EMAIL PROTECTED] wrote: It's been standard since at least SRV 2.2. See the servlet spec, section 7.1. E.g., SRV.7.1.1 Cookies Session tracking through HTTP cookies is the most used session tracking mechanism and is required to be supported by all servlet containers. The container sends a cookie to the client. The client will then return the cookie on each subsequent request to the server, unambiguously associating the request with a session. The name of the session tracking cookie must be JSESSIONID. Max Cooper wrote: I think it was Tomcat-specific at one time, but I think it is in the Servlet spec now. -Max - Original Message - From: Daniel Joshua [EMAIL PROTECTED] To: 'Struts Users Mailing List' [EMAIL PROTECTED] Sent: Monday, July 28, 2003 3:47 AM Subject: [OT] Is jsessionid specific to Tomcat or generic to all web containers? Quick question. Is jsessionid specific to Tomcat or generic to all web containers? Regards, Daniel - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [OT] Is jsessionid specific to Tomcat or generic to all web containers?
--- Craig R. McClanahan [EMAIL PROTECTED] wrote: 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=testqry2=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. Ah, they definitely need to make that clearer in the spec. I had read that sentence but only interpreted it to mean a query string parameter. Thanks for the clarification. David Craig - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [OT] Is jsessionid specific to Tomcat or generic to all web containers?
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=value1param2=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=testqry2=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]
