Project

General

Profile

Bug #1978

mod_expire sends incorrect max-age when using mtime

Added by zezo about 7 years ago. Updated about 7 years ago.

Status:
Fixed
Priority:
Normal
Assignee:
-
Category:
mod_expire
Target version:
Start date:
2009-05-10
Due date:
% Done:

100%

Missing in 1.5.x:

Description

mod_expire sets Cache-Control: max-age= to the configured interval, and not to the actual stamp.

According to rfc2616, max-age overrides Expires:, and in effect the 'modification' directive turns to 'access'

All tested browsers (IE,Opera,FF,Chrome) comply with the RFC.

Discovered while trying to serve images that change 4 times/day at known moments.

The attached patch shoudt fix this.

max-age.patch View (953 Bytes) zezo, 2009-05-10 10:11

Associated revisions

Revision 2503 (diff)
Added by stbuehler about 7 years ago

Fix max-age value in mod_expire for 'modification' (fixes #1978)

Revision 69987ea9 (diff)
Added by stbuehler about 7 years ago

Fix max-age value in mod_expire for 'modification' (fixes #1978)

git-svn-id: svn://svn.lighttpd.net/lighttpd/branches/lighttpd-1.4.x@2503 152afb58-edef-0310-8abb-c4023f1b3aa9

Revision 2504 (diff)
Added by stbuehler about 7 years ago

Fix max-age value in mod_expire for 'modification' (fixes #1978)

History

#1 Updated by icy about 7 years ago

  • Target version changed from 1.4.22 to 1.4.23

While at it, the ints should be changed to time_ts.

target version != affected version

#2 Updated by stbuehler about 7 years ago

  • Status changed from New to Fixed
  • % Done changed from 0 to 100

Applied in changeset r2503.

#3 Updated by stbuehler about 7 years ago

  • Estimated time deleted (0.10 h)

Also available in: Atom