-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hugo,
LASSIEGE Hugo wrote: > I trace the request between client and server and I see that the > jsessionid is set twice. Here is the trace : > > Request : > POST /appli/server/servlet/appliservlet HTTP/1.1 [snip] > Response : > HTTP/1.1 200 OK [snip] > Set-Cookie: JSESSIONID=6B5EA29A87F6D84C44BA15FCD307BF2E.MIDDLEWARE1; > Path=/appli/server > Set-Cookie: JSESSIONID=6B5EA29A87F6D84C44BA15FCD307BF2E.MIDDLEWARE1 > Request : > POST /appli/server/servlet/appliservlet HTTP/1.1 [snip] > Cookie: JSESSIONID=6B5EA29A87F6D84C44BA15FCD307BF2E.MIDDLEWARE1; > JSESSIONID=6B5EA29A87F6D84C44BA15FCD307BF2E.MIDDLEWARE1 Are you using single-sign-on? How about a proxy? What version of Tomcat are you using? > Anybody have ideas about this problem and how to solve it ? Well... does this extra cookie cause any actual problems? - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGk9kP9CaO5/Lv0PARAtK0AJsGWgiHTMnzx9RtktMorWwjpA7PmQCdGnp3 OlEXeynPz/T5c9zyJuVNyQ0= =87ox -----END PGP SIGNATURE----- --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
