DO NOT REPLY [Bug 21172] New: - Problem setting cookies on coyote connector

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21172>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21172

Problem setting cookies on coyote connector

           Summary: Problem setting cookies on coyote connector
           Product: Tomcat 4
           Version: 4.1.24
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Connector:Coyote JK 2
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: mvanr@bigfoot.com


I am using tomcat 4.1.24 and apache 2.0.43 with mod_jk2.  I have been using 
ajp13 as a connector because initially there were problems with isSecure() on 
the coyote connector that have now been fixed.  I tried the coyote connector 
again recently, and there seems to be a problem where addCookie blasts any 
cookie that has previously been set.   In my case, my code looked something 
like:

  doGet(...)
  {
     ...
     if (session.isNew())
        response.addCookie(myCookie);
     ...
  }

This caused the session tracking to go astray, and the JSESSIONID cookie not to 
be sent to the client.  Without the addCookie(), session tracking worked 
again.  

This bug is similar to http://nagoya.apache.org/bugzilla/show_bug.cgi?id=234, 
except it's worse (ajp13 seems to allow 2 cookies per response, while coyote 
allows only 1).  Using the ajp13 connector, the above code does not break the 
session tracking.

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org