At 09:16 AM 7/13/2001 +0200, Lutz Steinborn wrote:
>Good morning,
>
>this what a have figured out last night too.
>I Had this problem months ago with a different enviremont.
>And the only solution I've found was the same like you have done.
>
>So is where anybody here who has succesfully used WebKit.Cookie with
>c.setMaxAge(30*24*60*60) ?
>
>Regards
>
>Lutz
These cookie issues came up earlier so I searched through my mailbox and
re-read the old thread. (Anyone notice that Geocrawler does a _really_ bad
job at searches? (and therefore maybe archiving.))
What I gleaned was that:
- expires is the old Netscape standard, still supported by most, if not
all, browsers
- max-age is the "new" RFC 2109 standard. Support level unknown (to me).
- Jakarta (Java servlets) seems to use expires for cookie version 0 and
max-age for anything else. I'm not sure what the default cookie version is
in Jakarta.
- My preference is to preset setMaxAge() to cookie users and "do the right
thing" internally.
I will forward the 2 most interesting messages from the thread to the list.
-Chuck
_______________________________________________
Webware-discuss mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/webware-discuss
