Ok, I give up here. Why is JRun handing out a cookie that expires at
24:38:33 !?!?! HTTP specs say cookie times should be in RFC 822 format:
0-23. Why is JRun handing out a 24:xx:xx cookie?!?
The reason I ask is that our own cookie (SEID) seems to be using a 1-24
format and I think this is causing us some problems.
We are using javax.servlet.http.Cookie and setMaxAge(). Does JRun use this
as well to set it's cookies? Does this point to some bug in the JRE?
Mmm, what's up?
HTTP/1.1 200 OK
Server: Microsoft-IIS/5.0
Date: Fri, 15 Sep 2000 00:38:33 GMT
Set-Cookie: SEID=2031033;expires=Tue, 28-Aug-2001 05:58:33 GMT;path=/
Set-Cookie: jsessionid=7121968978313336;expires=Wed, 15-Sep-1999 24:38:33
GMT;path=/
Expires: Thu, 01 Dec 1994 16:00:00 GMT
Connection: Close
Cache-Control: no-cache="set-cookie,set-cookie2"
Content-Type: text/html; charset=ISO-8859-1
---
Jeff Stevens
System Engineer
Tradeout
(617) 283-3545
------------------------------------------------------------------------------
Archives: http://www.egroups.com/group/jrun-interest/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/jrun_talk
or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the
body.
