https://issues.apache.org/bugzilla/show_bug.cgi?id=44679
--- Comment #44 from krystian <krystian.no...@gmail.com> 2011-09-20 18:32:13 UTC --- Observing the comments here I would have to support it as being an interoperability issue between other, non Java platforms/languages. As an example we can put here Resin as Java-PHP interop bridge: http://bugs.caucho.com/view.php?id=4767 It boils down to supporting array cookies (multidimensional arrays in fact) in PHP as described in: http://php.net/manual/en/language.variables.external.php#language.variables.external.cookies http://php.net/manual/en/function.setcookie.php#example-3780 http://www.developertutorials.com/tutorials/php/articlename-050526-1149/ Of course one can put one RFC against another, but fortunately, at least on different javax.servlet.http.Cookie implementations there are possible workarounds as in: http://java.net/jira/browse/GLASSFISH-10850?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel http://java.net/jira/browse/GLASSFISH-10945?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel advising to use (in some implementations e.g. from javax.servlet-api-3.0.1) system property defining legacy/backward-compatibility mode: "org.glassfish.web.rfc2109_cookie_names_enforced" system property So it seems that the subject still lives, is viable, important and cannot be just muted by "parse the cookie header yourself". Cheers, Krystian -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
