You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tomcat.apache.org by bu...@apache.org on 2001/10/19 19:52:51 UTC

DO NOT REPLY [Bug 4295] New: - Cookies not following RFC2109

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=4295>.
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=4295

Cookies not following RFC2109

           Summary: Cookies not following RFC2109
           Product: Tomcat 4
           Version: 4.0.1 Final
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Critical
          Priority: Other
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: cmanolache@yahoo.com


Acording to RFC2109, the cookie name is a token and the value is a 'value', as defined in RFC2068 ( HTTP/1.1 ). The 'value' is defined as token or quoted string. 
Netscape cookies are also defined as 'string that does not include space, comma, semi-column'.
The current implementation is URL-encoding the name and value. This creates problems for applications that use cookies. Cookies are alse URL-decoded when received, which is also non standard.