Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 277 invoked from network); 10 Oct 2004 17:58:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 10 Oct 2004 17:58:16 -0000 Received: (qmail 89071 invoked by uid 500); 10 Oct 2004 17:58:12 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 89035 invoked by uid 500); 10 Oct 2004 17:58:12 -0000 Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@ws.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 89026 invoked by uid 99); 10 Oct 2004 17:58:12 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=RCVD_BY_IP,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of davanum@gmail.com designates 64.233.170.203 as permitted sender) Received: from [64.233.170.203] (HELO mproxy.gmail.com) (64.233.170.203) by apache.org (qpsmtpd/0.28) with ESMTP; Sun, 10 Oct 2004 10:58:10 -0700 Received: by mproxy.gmail.com with SMTP id 78so159462rnk for ; Sun, 10 Oct 2004 10:58:09 -0700 (PDT) Received: by 10.38.82.20 with SMTP id f20mr1207158rnb; Sun, 10 Oct 2004 10:58:08 -0700 (PDT) Received: by 10.38.171.72 with HTTP; Sun, 10 Oct 2004 10:58:08 -0700 (PDT) Message-ID: <19e0530f04101010586c402a34@mail.gmail.com> Date: Sun, 10 Oct 2004 13:58:08 -0400 From: Davanum Srinivas Reply-To: dims@apache.org To: axis-dev@ws.apache.org, ron.marchi@ugs.com Subject: Re: [jira] Updated: (AXIS-1080) Axis 1.1 doen't support multi-cookies In-Reply-To: <185160716.1097259352750.JavaMail.apache@nagoya> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <185160716.1097259352750.JavaMail.apache@nagoya> X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Ron, Can you please submit a diff (upload to jira) against latest cvs sources? thanks, dims On Fri, 8 Oct 2004 11:15:52 -0700 (PDT), axis-dev@ws.apache.org wrote: > The following issue has been updated: > > Updater: Ron Marchi (mailto:ron.marchi@ugs.com) > Date: Fri, 8 Oct 2004 11:15 AM > Comment: > Here is another solution to this problem. > It maintains the path information in the set-cookie, but assumes that since the cookie was returned for this service the path must be good. > It also puts the Set-Cookie value on the Message Context, allowing a JAX-RPC Handler access to both the Cookie and Set-Cookie properties for management of cookies between Services. > Changes: > Attachment changed to CookeFix.zip > --------------------------------------------------------------------- > For a full history of the issue, see: > > http://issues.apache.org/jira/browse/AXIS-1080?page=history > > --------------------------------------------------------------------- > View the issue: > http://issues.apache.org/jira/browse/AXIS-1080 > > Here is an overview of the issue: > --------------------------------------------------------------------- > Key: AXIS-1080 > Summary: Axis 1.1 doen't support multi-cookies > Type: Bug > > Status: Reopened > > Project: Axis > Components: > Basic Architecture > Versions: > 1.1 > > Assignee: > Reporter: Olivier PEPIN > > Created: Wed, 8 Oct 2003 10:31 AM > Updated: Fri, 8 Oct 2004 11:15 AM > Environment: Operating System: All > Platform: All > > Description: > Scenario : The Axis Webservice as a session scope deploy on weblogic > The client uses setMaintainSession(true); > A filter in front of the AxisServlet set a extra cookie (for load balancing) > > * First call > * Client header : > No cookie sent > * Server header: > Set-Cookie: JSESSIONID=AAAAAA > Set-Cookie: LBCOOKIE=BBBBBBB > > * Second call > * Client header : > Cookie: JSESSIONID=AAAAAAA(only one cookie set) > * Server header: > Set-Cookie: LBCOOKIE=CCCCCCC (new lb cookie) > > * Third call > * Client header : > Cookie: LBCOOKIE=CCCCCCC (only one cookie set this time the other is lost) > * Server header: > Set-Cookie: LBCOOKIE=DDDDDD( new session created) > > Problems: > * Only one cookie is stored for each call > * If a cookie is already stored in the MessageContext, it is deleted by a new > cookie > > Results: > * Statefull services is not working > * Load balancing is not working > > Bug analysis : > The HTTPSender (and CommonsHTTPSender) classe stores headers as Hashmap. > * It does not support multiple Set-Cookie: headers > * It do not send back multiple cookies. > The same way for the MessageContext that stores the "cleaned" cookies as a > HashMap. > * Old cookie is deleted (JSESSIONID), if a new cookie is send (LBCOOKIE) on a > next call > > PS: This bug has been fixed on SOAP 2.3.1 some time ago > > --------------------------------------------------------------------- > JIRA INFORMATION: > This message is automatically generated by JIRA. > > If you think it was sent incorrectly contact one of the administrators: > http://issues.apache.org/jira/secure/Administrators.jspa > > If you want more information on JIRA, or have a bug to report see: > http://www.atlassian.com/software/jira > > -- Davanum Srinivas - http://webservices.apache.org/~dims/