On 22/06/2016 11:29, Mark Thomas wrote: > On 22/06/2016 09:28, Markus Näher wrote:
>> In the web console of firefox, I could see that the session cookie was >> set with the path /jsf%5ftest, while other cookies (set by myfaces) were >> correctly set with the path /jsf_test. >> It looks like firefox treats /jsf_test and /jsf%5ftest as different >> pathes and therefore does not send the session cookie with the next >> request, while chromium ignores the difference. > > I see a similar issue if I rename the examples web application to > "exa_mples". It shouldn't take me too long to figure out where things > are going wrong. Tomcat is correctly setting the path for the session cookie as "/exa_mples" > I'll keep that in mind once I figure out the root cause. It may impact > how we fix this. The problem is that FireFox, by default, encodes all URIs and doesn't take account of the encoding when matching URIs to cookie paths. Failing to account for encoding looks like a FireFox bug to me. A possible work-around is to disable the automatic encoding of URLs that FireFox provides by setting network.standard-url.encode-utf8 to false under about:config. >> Unfortunately, my real-world productive project has an underscore in >> it's name too, but as many users have bookmarked it, I can't just rename >> it. >> >> Is this a bug in tomcat ? > > At this point I'd say it is likely but until I dig into this to figure > out exactly what the root cause is, I can't be sure. No, it is a FireFox bug. And a long standing one at that. https://bugzilla.mozilla.org/show_bug.cgi?id=665851 Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
