Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@www.apache.org Received: (qmail 1031 invoked from network); 13 Jan 2004 11:04:44 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 13 Jan 2004 11:04:44 -0000 Received: (qmail 56943 invoked by uid 500); 13 Jan 2004 11:04:12 -0000 Delivered-To: apmail-jakarta-tomcat-dev-archive@jakarta.apache.org Received: (qmail 56680 invoked by uid 500); 13 Jan 2004 11:04:09 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Developers List" Reply-To: "Tomcat Developers List" Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 56658 invoked from network); 13 Jan 2004 11:04:09 -0000 Received: from unknown (HELO guildo.signal7.de) (62.138.167.130) by daedalus.apache.org with SMTP; 13 Jan 2004 11:04:09 -0000 Received: (qmail 24266 invoked by uid 1001); 13 Jan 2004 11:04:22 -0000 Received: from drafi.intranet.signal7.de (HELO signal7.de) (194.162.55.194) by 192.168.7.2 with SMTP; 13 Jan 2004 11:04:22 -0000 Message-ID: <4003D0AD.804@signal7.de> Date: Tue, 13 Jan 2004 12:04:13 +0100 From: =?ISO-8859-1?Q?Robert_Kr=FCger?= User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6a) Gecko/20031026 Thunderbird/0.4a X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tomcat Developers List Subject: Coyote Session-Handling Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Hi, we're currently porting a number of applications from Orion to Tomcat 5 and I ran into a (not so dramatic) problem. I set up 2 virtual hosts (i.e. 2 Services) running on the same host but different port and deployed two web applications. Now it is not possible to use these two web applications simultaneously as they interfere with each other's session, i.e. the browser sends the JSESSIONID cookie to both sites (which is correct according to RFC 2109, I think, because they only differ in port) but Coyote considers the sent session ID invalid whenever I change from one application to the other and sets a new one effectively killing the session I had open in the other application. Is that behaviour intentional? The code of CoyoteRequest.doGetSession looks as if that was the case. One possible solution for that would be to allow opening a new session under the JSESSIONID that was passed to the web application (in my case the second one accessed). Are you aware of any negative implications of that approach (I believe orion does it that way)? In my case the current behaviour means that I cannot deploy frontend and backend of my application on the same host only differing in port, which of course can be overcome by using another host name but I would like to know if you think this limitation could be removed. Thanks in advance, Best regards, Robert -- ________________________ Robert Kr�ger Signal7 GmbH Br�der Knauss Str. 79 64285 Darmstadt Germany --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org