-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Rainer,
On 9/4/2009 12:52 AM, Rainer Jung wrote: > On 03.09.2009 23:31, Christopher Schultz wrote: >> Whenever a client browses to webapps found on / and /foo, the requests >> to /foo will get TWO cookies, and confusion may occur (I'm not sure what >> mod_jk will do in this situation... Rainer?). > > Not sure either :( > > Even if I looked at the code now, I wouldn't take it for granted, that > the behaviour can't change. Agreed. I don't have a cluster handy to test, but it would be good to know what mod_jk actually does in the case where multiple JSESSIONID cookies exist and have different jvmRoute suffixes. > Actually I'm not even sure what the browser is supposed to send (the > same cookie multiple times, or only the one with the longest path > match). My experience was that /both/ cookies were sent (which makes sense, since there's no prohibition against the same cookie name being used more than one time when a different path is used). - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkqhJEcACgkQ9CaO5/Lv0PDpggCgv1aVrfTiq9MH1SF2Td4Ha3EP iY0AoLnXxKeQ6iKeermF2JbvCRjEGoaQ =I2jx -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
