Re: HTTP date format: RFC 850 or RFC 1036

• Mail folder: WWW Talk Oct 93-present
• Next message: Rob McCool: "Re: CGI server indexing with WAIS"
• Previous message: Frederick G.M. Roeber: "Re: Attaching docs, Virtual images"
• Maybe in reply to: Rob McCool: "Re: HTTP date format: RFC 850 or RFC 1036"

Message-id: <9312171051.AA17686@void.ncsa.uiuc.edu>
From: robm@ncsa.uiuc.edu (Rob McCool)
Date: Fri, 17 Dec 1993 04:51:43 -0600
In-Reply-To: "Roy T. Fielding" <fielding@simplon.ICS.UCI.EDU>
       "Re: HTTP date format: RFC 850 or RFC 1036" (Dec 15,  8:19pm)
X-Mailer: Mail User's Shell (7.2.5 10/14/92)
To: "Roy T. Fielding" <fielding@simplon.ICS.UCI.EDU>,
        Tony Sanders <sanders@bsdi.com>
Subject: Re: HTTP date format: RFC 850 or RFC 1036
Cc: www-talk@www0.cern.ch, Tim Berners-Lee <timbl@www0.cern.ch>
Content-Length: 714

/*
 * Re: HTTP date format: RFC 850 or RFC 1036  by "Roy T. Fielding" (fielding@simplon.ICS.UCI.EDU)
 *    written on Dec 15,  8:19pm.
 *
 * Break?  The output format of the date makes no difference to the HTTP
 * server -- only to the clients (like the one I'm building).  As for a change,
 * the NCSA httpd server just changed its date format to supposedly be RFC822
 * (see the announcement) and the fact that it is not should be pointed out.
 */

I got the RFC number wrong in the announcement; I used Tony's server as a
model of what the HTTP protocol specifes since it was faster than looking
through the RFC, and it encouraged consistency (if Plexus outputs that way,
now NCSA does the same). Sorry.

--Rob