Apple

NSTimestamp oneYear = new NSTimestamp().timestampByAddingGregorianUnits(1, 0, 0, 0, 0, 0);
NSTimestamp threeMonths = new NSTimestamp().timestampByAddingGregorianUnits(0, 3, 0, 0, 0, 0);
a_rsp.addCookie(new WOCookie("key_a_" + i, "v:" + i, "/", null, oneYear, false));
a_rsp.addCookie(new WOCookie("key_b_" + i, "v:" + i++, "/", null, threeMonths, false));

I suspect my earlier issue is maybe a bug in how Safari handles the timeout duration value (possibly treating it as milliseconds rather than seconds)

I have not been able to actually reproduce the behavior with cookie timeouts with max-age in Safari 4, but I have heard at least one other report of this (specifically on Windows) ... I basically tested all the variants in every browser:

The final story is that the Netscape-style cookies are the most compatible in every browser (triggered, mostly, by using the NSTimestamp constructor) ... max-age seems to have some sketchy support in IE, and Safari 3 for Win appears to use the native cookie jar (Safari 4 changed to use CFNetwork's).

References:
	>Odd cookie expiration behaviour (Safari related?) (From: Mark Gowdy <email@hidden>)
	>Re: Odd cookie expiration behaviour (Safari related?) (From: Mike Schrag <email@hidden>)
	>[Solved] Odd cookie expiration behaviour (Safari related?) (From: Mark Gowdy <email@hidden>)