Return-Path: 
 <bugs-return-4037-apmail-httpd-bugs-archive=httpd.apache.org@httpd.apache.org>
Delivered-To: apmail-httpd-bugs-archive@httpd.apache.org
Received: (qmail 54477 invoked by uid 500); 7 Nov 2002 23:34:42 -0000
Mailing-List: contact bugs-help@httpd.apache.org; run by ezmlm
Precedence: bulk
List-Post: <mailto:bugs@httpd.apache.org>
List-Help: <mailto:bugs-help@httpd.apache.org>
List-Unsubscribe: <mailto:bugs-unsubscribe@httpd.apache.org>
List-Subscribe: <mailto:bugs-subscribe@httpd.apache.org>
Reply-To: "Apache HTTPD Bugs Notification List" <bugs@httpd.apache.org>
Delivered-To: mailing list bugs@httpd.apache.org
Received: (qmail 54466 invoked from network); 7 Nov 2002 23:34:42 -0000
Date: 7 Nov 2002 23:35:44 -0000
Message-ID: <20021107233544.19265.qmail@nagoya.betaversion.org>
From: bugzilla@apache.org
To: bugs@httpd.apache.org
Cc: 
Subject: DO NOT REPLY [Bug 14376] New:  -
    mod_proxy overwrites Date header
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

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

           Summary: mod_proxy overwrites Date header
           Product: Apache httpd-2.0
           Version: 2.0.43
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: mod_proxy
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: apache-bugs@wotevah.com


It appears that mod_proxy overwrites the Date header with the local date.
Mine is configured as a Reverse Proxy (have not tried the other way).
The date header is in the proper format (comes from an Apache 1.3 server).

This should not happen because this way the client loses the reference for
the Expires header (which passes through unmodified).

Below are two sets of response headers I tested with. The first one is
the backend server accessed directly, the second is via the proxy, at
about 20 seconds time difference. The time on the proxy is 2-3 minutes
behind the backend's. The frontend always sets the expiration date to 
same value as date.

HTTP/1.1 200 OK
Date: Thu, 07 Nov 2002 21:41:15 GMT
Server: Apache/1.3.27 (Unix)
Cache-control: no-cache
Content-Length: 1924
Connection: close
Content-Type: text/html; charset=UTF-8
Expires: Thu, 07 Nov 2002 21:41:15 GMT

HTTP/1.0 200 OK
Date: Thu, 07 Nov 2002 21:38:31 GMT
Server: Apache/1.3.27 (Unix)
Cache-control: no-cache
Content-Type: text/html; charset=UTF-8
Expires: Thu, 07 Nov 2002 21:41:37 GMT
Via: 1.1 <proxyhostname>
Connection: close

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