Bug 35245 - cache ignores max-age cache-directive in requests to max-aged responses
Summary: cache ignores max-age cache-directive in requests to max-aged responses
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_cache_disk / mod_disk_cache (show other bugs)
Version: 2.0.54
Hardware: All All
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL: http://coad.measurement-factory.com/c...
Keywords: MassUpdate, RFC
Depends on:
Reported: 2005-06-06 21:22 UTC by Co-Advisor
Modified: 2018-11-07 21:09 UTC (History)
0 users

test case trace (14.90 KB, text/html)
2005-06-06 21:32 UTC, Co-Advisor

Note You need to log in before you can comment on or make changes to this bug.
Description Co-Advisor 2005-06-06 21:22:03 UTC
Looks like a possible RFC 2616 MUST violation.
Apache cache ignores max-age cache-control 
directive in the request (possibly only when
the response has another max-age, which indicated
that the response is still fresh).

See attached traces for details and ways to reproduce
some of the violations mentioned above.

Test case IDs in the trace link to human-oriented
test case description and RFC quotes, if available.

Note: A related fixed bug 15869 deals with the 
response max-age. This bug is about the request
Comment 1 Co-Advisor 2005-06-06 21:32:16 UTC
Created attachment 15318 [details]
test case trace

Note that the response has its own max-age.
The response is fresh according to its own
max-age, but not according to the request max-age.
RFC 2616 says request max-age MUST be honored here.
We do not know whether the response max-age is a
factor (or all request max-age directives are ignored).
Comment 2 William A. Rowe Jr. 2018-11-07 21:09:55 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.