os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Hope I'm not stepping on anybody's toes... Add a note regarding date issues

Browse source 
in fetch(1) and the HTTP protocol.
This commit is contained in:
Garrett Wollman 1999-01-15 17:14:08 +00:00
parent a83b192860
commit 492cc0b8eb
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=4065
1 changed files with 14 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

16
en/y2kbug.sgml
View file

@ -1,9 +1,9 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY date "$Date: 1999-01-13 21:17:49 $">
<!ENTITY date "$Date: 1999-01-15 17:14:08 $">
<!ENTITY title 'Year 2000 Compatibility (aka "Millennium Bug")'>
<!ENTITY % includes SYSTEM "includes.sgml"> %includes;
]>
<!-- $Id: y2kbug.sgml,v 1.15 1999-01-13 21:17:49 danny Exp $ -->
<!-- $Id: y2kbug.sgml,v 1.16 1999-01-15 17:14:08 wollman Exp $ -->
<html>
&header;
@ -120,6 +120,18 @@
Now adjusted to allow two digit years for 1970-2069. The function
does not allow for century non-leap years - y2k1 alert!
</dd>
<dt><a href="http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.bin/fetch/http.c.diff?r1=1.22&amp;r2=1.23">fetch/http.c</a></dt>
<dd>The HTTP protocol includes an obsolete date format which uses a
two-digit year. Previous versions of fetch would interpret all such
dates in the 1900s; subsequent to this revision, the pivot described
in <a href="ftp://ftp.cdrom.com/pub/internet/rfc/rfc2068.txt">RFC
2068</a> is employed, which causes two-digit years to be interpreted
as always belonging to the current century unless they would be
50 or more years in the future. Since the HTTP servers which
use this obsolete format are no longer widespread, this is not expected
to have a significant impact.
</dd>
</dl>