Bug 48585 - mod_cache no longer caches expired content
Summary: mod_cache no longer caches expired content
Status: RESOLVED LATER
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_cache (show other bugs)
Version: 2.2.14
Hardware: All All
: P2 enhancement (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords: MassUpdate
Depends on:
Blocks:
 
Reported: 2010-01-20 14:11 UTC by Philip Pickett
Modified: 2018-11-07 21:08 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philip Pickett 2010-01-20 14:11:10 UTC
As of Apache 2.2.4, mod_cache no longer caches expired content.  This is due to the changed associated with rev. http://svn.apache.org/viewvc?view=revision&revision=450055.  While this change may make sense for the majority of cases, we have a scenario where the previous behavior was being made us of.

As an enhancement, I'd like to request that the previous behavior be selectable via a configuration directive.
Comment 1 Eric Covener 2010-01-20 14:14:29 UTC
FWIW, we chatted about this on IRC and it sounded like they benefit from having an expires-in-the-past file sitting in the cache, and when clients request it, the backend will return 304 in response to if-modified-since (but continue to set the backdated expires, presumably)
Comment 2 William A. Rowe Jr. 2010-01-20 14:20:09 UTC
Yup, that's the only use case I can think of, Eric.

On the other hand, we can't revert, since that would waste disk space and was
an undesireable side effect for the 'typical user'.

So leaving 2.2.4 behavior as the default, it does make sense to accept a new
option, e.g. CacheExpired On|Off [default; off] to disable the current expiree
test.
Comment 3 William A. Rowe Jr. 2018-11-07 21:08:10 UTC
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd.

As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd.

If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question.

If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with.

Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.