1
0
mirror of https://github.com/php/web-php.git synced 2026-03-24 07:12:16 +01:00

Clarify the Y2K cookie issue a bit

This commit is contained in:
Rasmus Lerdorf
1998-06-30 17:54:39 +00:00
parent dbda9c7117
commit cd170d378f

View File

@@ -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.<P>
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 <b>y2k_compliance</b>
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 &quot;13&quot;, 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 <b>y2k_compliance</b> configuration setting available in
the <i>php3.ini</i> file.
<?
commonFooter();