Return-Path: owner-new-httpd Received: by taz.hyperreal.com (8.6.12/8.6.5) id QAA06513; Tue, 15 Aug 1995 16:40:48 -0700 Received: from neon.netscape.com by taz.hyperreal.com (8.6.12/8.6.5) with ESMTP id QAA06508; Tue, 15 Aug 1995 16:40:45 -0700 Received: (from robm@localhost) by neon.netscape.com (950215.SGI.8.6.10/8.6.9) id QAA15101; Tue, 15 Aug 1995 16:40:08 -0700 Date: Tue, 15 Aug 1995 16:40:08 -0700 From: Rob McCool Message-Id: <199508152340.QAA15101@neon.netscape.com> To: new-httpd@hyperreal.com Subject: Re: last-modified date checks In-Reply-To: <199508152148.RAA32659@beach.w3.org> References: <199508150146.SAA03933@neon.netscape.com> <199508152148.RAA32659@beach.w3.org> Sender: owner-new-httpd@apache.org Precedence: bulk Reply-To: new-httpd@apache.org /* * "Re: last-modified date checks " by Roy Fielding * written Tue, 15 Aug 1995 17:48:04 -0400 * * Tell the browser people to fix their bugs first, before changing * the server. I read the http-wg list first, so I've already * answered this question there today. Yeah, he kind of surprised me on that one. * I do think it would be wise for a server to complain about bad time * data on the files it serves. Complain to who, though? Log an error? * I think it is reasonable for the server to * refuse to send a Last-Modified date if the date is later than the * time it is serving the file. */ That sounds reasonable. I happen to agree that having Netscape stop sending IMS for a forced reload would be a good thing. --Rob