Re: [jetty-discuss] Problems with cookie.setMaxAge in Jetty 4.2.12

[Greg W. <gr...@mo...>]

You fix is correct and has already been put into 4.2.14RC0

cheers


Perry Arnold wrote:
> Hi, we recently moved from Jetty 3.1.5 to Jetty 4.2.12 and now our 
> cookies no longer get the right expiration date. We're using 
> cookie.setMaxAge() with very small values (one to ten minutes) and what 
> we're finding is that if you run this code in the GMT timezone, the 
> expiration comes out exactly right. If you run it outside of the GMT 
> timezone, it's off by the timezone offset (expirations are too long east 
> of GMT, nonexistent west of GMT).
> 
> We noticed that org.mortbay.http.HttpFields has changed in one minor way 
> between these versions:
> 
> the line:
> 
> buf.append(HttpFields.__dateSend.format(new 
> Date(System.currentTimeMillis()+1000L*maxAge)));
> 
> has become:
> 
> buf.append(HttpFields.__dateCookie.format(new 
> Date(System.currentTimeMillis()+1000L*maxAge)));
> 
> This new static member, __dateCookie, doesn't ever have setTimeZone(tz) 
> called on it like __dateSend does.
> 
> So, after all that, my questions are:
> 
> * Has anybody else run into this?
> * Are we doing something wrong? Should we be setting the timezone 
> somewhere when creating the cookie or the response?
> * Could this code be wrong?
> 
> We put in a temporary fix that calls setTimeZone(tz) on __dateCookie 
> just like __dateSend, but we're not sure if that's just a hack and we're 
> doing something wrong or what.
> 
> thanks,
> 
> ---Perry
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> SourceForge.net hosts over 70,000 Open Source Projects.
> See the people who have HELPED US provide better services:
> Click here: http://sourceforge.net/supporters.php
> _______________________________________________
> jetty-discuss mailing list
> jet...@li...
> https://lists.sourceforge.net/lists/listinfo/jetty-discuss
>