tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From srevi...@g88.net
Subject Re: Cookie problem max age problem - Best practice to solve it
Date Thu, 31 Jul 2003 12:31:31 GMT
> From: Jose Euclides da Silva Junior - DATAPREVRJ
> Subject: Cookie problem max age problem - Best practice to solve it

> this question is very important to me. My application works with an external
> authentication app ( like a plugin).When the user is logged, a browser
> cookie is created. The problem stays whenever the user asks for a logout
> process and the external app tries to "kill" its cookie (created before by
> the app), probably setting cookie's max age to 0, i guess. But TomCat doesnt
> know that this cookie is already killed, because it just fetch the name and
> value.  So, i would like any tips about best practice on solving this kind
> of problem.

Cookie exchanges fall into one of two categories:

 - what the server sends to the client
 - what the client sends back to the server

Tomcat wouldn't fetch the value; the client's browser sends it.

Setting the max age of a cookie to zero is the proper way to delete a
cookie.  When doing the deletion, are you sure that the name, domain,
and path values are identical to the ones used when the cookie was
initially set?

-- 
Steve

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org


Mime
View raw message