-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Tim,
Timothy Washington wrote: | Thanks for the feedback so far. I actually kept the interactions as | simple as possible exactly to minimize any unknown behaviour. There's no | SSL or filters in the application yet. So, there's pretty much nothing in the way. Where is your client in relation to Tomcat? Is this on localhost, or over a network? Is is possible that you have a firewall or proxy that is removing the Set-Cookie header? I would imagine that some corporate firewalls do that to enforce a no-cookies policy. What if you try to set your own header on the response (before or after the 'perform' method is invoked)? Try something like: response.addHeader("my-custom-header", "foo"); ...and see if that makes it back to the client. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkgPSTkACgkQ9CaO5/Lv0PCC5QCfZCdZ96e6JccC9e/KuwDVqKwL 87wAn29FZvSE+GJgmVlPJMFC+MLsrR/y =0J/F -----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]