DO NOT REPLY [Bug 4295] - 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 [EMAIL PROTECTED] changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2002-02-22 04:03 --- Fixed on both branches. Nightly for 02/22 will have the fix. NOTE: THIS FIX MAY BREAK APPLICATIONS WHICH WOULD RELY ON CONTAINER PROVIDED URL ENCODING / DECODING. NOTE: This particular fix will be mentioned in the release notes for the next Tomcat 4.0.x release. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 4295] - 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 [EMAIL PROTECTED] changed: What|Removed |Added CC||tomcat- ||[EMAIL PROTECTED] Priority|Other |Low -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 4295] - 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 --- Additional Comments From [EMAIL PROTECTED] 2001-10-24 11:47 --- And what do you suggest we do instead ? Did you try removing the calls to encode in the CookieTools ? (The calls to decode are somewhere else, but it should be quite obvious too). Does it work well without them ? If it does, maybe you can commit this in the HEAD branch to see if it doesn't create any problems (can't see why it would ...).