From cd170d378fc8bad3ecfecf28cd6fbffacf4cb09a Mon Sep 17 00:00:00 2001 From: Rasmus Lerdorf Date: Tue, 30 Jun 1998 17:54:39 +0000 Subject: [PATCH] Clarify the Y2K cookie issue a bit --- y2k.php3 | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/y2k.php3 b/y2k.php3 index b568b5217..03a029a49 100644 --- a/y2k.php3 +++ b/y2k.php3 @@ -3,12 +3,16 @@ require("shared.inc"); commonHeader("Year 2000 Compliance and PHP"); ?> Like Perl, PHP is about as Year 2000 compliant as your pencil. It is the applications -you write with PHP you need to worry about, not PHP itself. +you write with PHP you need to worry about, not PHP itself.

-There is an issue with the dates in cookies. We have found that not all browsers understand -4-digit years in the cookie expiry time. But they all accept 2-digit years. If you do not -care about these non-compliant browsers, then feel free to change the y2k_compliance -configuration setting in the php3.ini file. +There is an issue with the dates in cookies. Netscape originally specified that the expiry +date on a cookie should be in a 2-digit year format. Due to all the y2k hype, they decided to +change this behaviour in Netscape 4 and up. This doesn't mean that the 2-digit year is not +y2k compliant. A 2-digit year of "13", for example will be understood as the year +2013 in Netscape. All browsers understand this 2-digit format, and thus this is the +default in PHP. Some y2k fanatics still insist on never using a 2-digit year no matter +what, and for those people PHP has a y2k_compliance configuration setting available in +the php3.ini file.