Mailing-List: contact bugs-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache HTTPD Bugs Notification List" <bugs@httpd.apache.org>
Date: 8 Nov 2002 03:12:23 -0000
Message-ID: <20021108031223.23371.qmail@nagoya.betaversion.org>
From: bugzilla@apache.org
To: bugs@httpd.apache.org
Cc: 
Subject: DO NOT REPLY [Bug 14376]  -
    mod_proxy overwrites Date header

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14376>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14376

mod_proxy overwrites Date header


------- Additional Comments From apache-bugs@wotevah.com  2002-11-08 03:12 -------
The conclusion that the proxy must set the Date header when it has already been
provided by the origin server cannot be inferred from the two paragraphs quoted
(since the message is not originated on the proxy).

Using the rfc822 analogy mentioned in the text would imply a mail relay changing
the Date: header as the email passes through it, even if there is one already 
there that respects the format. That does not happen.

The proxy's changing of the date makes the Expires header as unreliable as the
time on the proxy machine, because other than the Date header, the client has 
no way to know the time reference of the origin server. That essentially makes
Expires unusable for anything other than very distant times in the future
(depending on how much the proxy time is off).

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org