Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 8050 invoked by uid 500); 10 Jun 2002 23:27:36 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 8027 invoked from network); 10 Jun 2002 23:27:35 -0000 Message-ID: <3D0535D6.4050206@slive.ca> Date: Mon, 10 Jun 2002 19:27:18 -0400 From: Joshua Slive User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc3) Gecko/20020523 X-Accept-Language: en-us, en, fr MIME-Version: 1.0 To: dev@httpd.apache.org Subject: Re: last modified header References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Jie Gao wrote: >>This is quite ambiguous, but I think this is how it should read: >> >>On the Apache web server, the last modified HTTP header is returned if >>the file is an HTML file. If it is a SHTML (or processed by >>mod_include), then the last modified header is only returned when >>the SHTML file is executable. And the XBitHack directive is set to "Full". > Otherwise, for a SHTML file with no >>executable bit set, no last modified information is returned. > > What would be desirable is a directive to send the last modified header > for all files. That would just be wrong. When content is dynamically generated, the "last-modified" date would need to be the same as the current time, so it wouldn't serve any purpose. Joshua.