On Fri, 24 Sep 1999, James Duncan Davidson wrote:
> On Fri, 24 Sep 1999, Dr. Dragomir D. Dimitrijevic wrote:
> > It looks like that addCookie method uses max age to encode
> > (calculate) the "Expires" tag, not "Max-Age" as one might expect.
> >
> > Is there any workaround?
>
> The problem may be that your server isn't providing a "Date" header
> as part of the HTTP response. WIthouth a Date header, the client is
> forced to calculate the cookie expiration against the local time,
> not the server time.
[ ... ]
Isn't this happening just because MaxAge really just involves
calculating and setting the date in the Expires field *on the server
side* and passing that to the client/browser, and then that date is
interpreted relative to the time on the client side? Does HTTP allow
expires being expressed as a "time *to* expiry" as opposed to a "time
*of* expiry"? If not, it would seem there's no way around this
problem of the time being off on the client end (assuming you've made
sure the time is correct on the server :-).
Milt Epstein
Research Programmer
Software/Systems Development Group
Computing and Communications Services Office (CCSO)
University of Illinois at Urbana-Champaign (UIUC)
[EMAIL PROTECTED]
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html