In that case, I would like to suggest a change to pass a copy of the Date header value in the environment to cgi-bin scripts. This would allow cgi-bin scripts to make sure that their Last-Modified headers aren't greater than their Date headers without having to make guesses about worst case latencies.
Thanks for looking into this. On Mon, Dec 21, 1998 at 01:44:31PM -0000, [EMAIL PROTECTED] wrote: > [In order for any reply to be added to the PR database, ] > [you need to include <[EMAIL PROTECTED]> in the Cc line ] > [and leave the subject line UNCHANGED. This is not done] > [automatically because of the potential for mail loops. ] > [If you do not include this Cc, your reply may be ig- ] > [nored unless you are responding to an explicit request ] > [from a developer. ] > [Reply only with text; DO NOT SEND ATTACHMENTS! ] > > > Synopsis: CGI Bin scripts can't override the Date header. > > State-Changed-From-To: open-closed > State-Changed-By: coar > State-Changed-When: Mon Dec 21 05:44:30 PST 1998 > State-Changed-Why: > The Date response field is one of those that Apache does > not permit to be overridden, since it refers to the time > at which the server began sending the response. Other > filters or operations that might be performed on a > script's output may delay this, or a script might emit > a bogus Date field, so this is one of the field reserved > to the server itself. See the last paragraph at > <http://www.apache.org/docs/mod/mod_headers.html>. > Class-Changed-From-To: sw-bug-change-request > Class-Changed-By: coar > Class-Changed-When: Mon Dec 21 05:44:30 PST 1998
