The second request will send the cookie information back to the server, at which point you would know if the client supports cookies or not (though, I don't think there'd be anyway to distinguish a client that *doesn't* support cookies from a new request entirely, that would be tricky).
If all you want to do is disable URL rewriting, you can do that easily enough through a Filter. Just wrap the response in a response wrapper, disabling the encodeUrl methods that are in the parent class (just override with dummy methods).
Eric Allen wrote:
I need to somehow disable URL rewriting for session tracking in my application. My designer uses <a:href tags all over and I don't want to change that, so I'm stuck with cookies. The problem is, tomcat doesn't appear to have any way of saying "if the user doesn't accept the session cookie, throw an exception" or something. I need a way to not allow the user to login if they do not support cookies. I am using Tomcat 5.0.18 and Struts 1.1. I am willing to come up with some kind of work around, but I can't find a way to hook into the low-level session handling stuff.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Brice Ruth, Sr. IT Analyst Fiskars Brands Inc http://www.fiskarsbrands.com/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
