httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 44518] New: Don't set expires header on HTTP redirect.
Date Sun, 02 Mar 2008 22:52:49 GMT

           Summary: Don't set expires header on HTTP redirect.
           Product: Apache httpd-2
           Version: 2.2.4
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: mod_expires

I have one Apache2 server setup at the front on port 80 serving static content
with ExpiresDefault "access plus 1 week". This server is configured to proxy
any requests that don't map to files in the document root to a second Apache2
server, for dynamic content (Django).

This works fine except for when my dynamic application generates a HTTP
redirect. On redirect to dynamic content, the first Apache2 server adds an
expires header which causes all the major browsers to pull the dynamic page
from their cache.

09:34:33 tailee@tetsuo ~$ curl -I
HTTP/1.1 302 Found
Date: Sun, 02 Mar 2008 22:34:54 GMT
Server: Apache/2.2.4 (Ubuntu) mod_python/3.3.1 Python/2.5.1
Vary: Cookie,Accept-Encoding
ETag: d41d8cd98f00b204e9800998ecf8427e
Content-Type: text/html; charset=utf-8
Cache-Control: max-age=604800
Expires: Sun, 09 Mar 2008 22:34:54 GMT

If I change my httpd.conf to ExpiresDefault "modification plus 1 week" the
expires header is NOT set, but this doesn't allow me to always keep static
content cached for 1 week from access.

Ideally, Apache2 should not set an expires header on redirects, or at least
there should be an option for httpd.conf to disable this behaviour.

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message