axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From axis-...@ws.apache.org
Subject [jira] Updated: (AXIS-1080) Axis 1.1 doen't support multi-cookies
Date Tue, 12 Oct 2004 15:31:53 GMT
The following issue has been updated:

    Updater: Ron Marchi (mailto:ron.marchi@ugs.com)
       Date: Tue, 12 Oct 2004 8:31 AM
    Comment:
Here is a CVS DIFF for the files in the CookieFix.zip
    Changes:
             Attachment changed to CookieFix-Diff.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: Tue, 12 Oct 2004 8:31 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


Mime
View raw message