-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Len,
Len Popp wrote: | Have you set cookies="false" in the app's <Context> declaration? | That'd do it. That wouldn't explain why Tomcat is adding the cookie to the response, but the cookie isn't making it across the wire. Tim, can you tell us a little more about the path of execution? I'm wondering if you are handling a request, modifying the response, and then forwarding (on the server side) to another process that maybe blanks-out the response and effectively kills the cookie or something like that. Is there any SSL involved at all? I wouldn't expect the behavior you describe to result from crossing an SSL boundary (I would expect the browser to get the cookie, but refuse to send it with the next request). Are there any special filters or valves that are being applied that might be modifying the behavior of the response? - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkgOnOkACgkQ9CaO5/Lv0PBUIQCdH1Q39DcjEM7dm6caLbHLEIrz PuQAnRuxPKiKx10EnGbV9fyM2ENTLSit =ULgz -----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]
