From owner-freebsd-hackers Sat May 31 16:08:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA21690 for hackers-outgoing; Sat, 31 May 1997 16:08:32 -0700 (PDT) Received: from punt-2.mail.demon.net (punt-2b.mail.demon.net [194.217.242.5]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id QAA21685 for ; Sat, 31 May 1997 16:08:28 -0700 (PDT) Received: from erlenstar.demon.co.uk ([194.222.144.22]) by punt-2.mail.demon.net id aa0516681; 31 May 97 23:54 BST Received: (from andrew@localhost) by erlenstar.demon.co.uk (8.8.5/8.8.5) id XAA29670; Sat, 31 May 1997 23:54:32 +0100 (BST) To: Brian Somers Cc: freebsd-hackers@freebsd.org Subject: Re: fetch References: <199705311510.QAA12461@awfulhak.demon.co.uk> From: Andrew Gierth In-Reply-To: Brian Somers's message of Sat, 31 May 1997 16:10:32 +0100 X-Mayan-Date: Long count = 12.19.4.3.15; tzolkin = 13 Men; haab = 13 Zip X-Attribution: AG Date: 31 May 1997 23:54:31 +0100 Message-ID: <87d8q7b6c8.fsf@erlenstar.demon.co.uk> Lines: 33 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>>>> "Brian" == Brian Somers writes: Brian> Hi, Brian> My ISP (demon.co.uk) sends http dates like this: Brian> Sat, 31-May-97 10:48:56 GMT Brian> According to http.c in the fetch sources, it's expecting Brian> a full year here, ie. Brian> Sat, 31-May-1997 10:48:56 ..... Brian> Has anyone any objection to me making it allow the first ? If fetch does not support the 31-May-97 format, then it violates the RFCs and should be fixed, regardless of whether it offends anyone's sensibilities concerning Y2K issues. Technically, Demon's server is misbehaving slightly, since the three allowed date formats are: Sun, 06 Nov 1994 08:49:37 GMT ; RFC 822, updated by RFC 1123 Sunday, 06-Nov-94 08:49:37 GMT ; RFC 850, obsoleted by RFC 1036 Sun Nov 6 08:49:37 1994 ; ANSI C's asctime() format and it is using the second of these with a shortened weekday name, but the robustness principle requires that fetch should cope with this. HTTP/1.1 requires that only the first form be generated, but the homepages server only does HTTP/1.0, which allows either of the first two forms. -- Andrew.