Bug 49990 - Feature request: implement ExpiresActive reset
Summary: Feature request: implement ExpiresActive reset
Status: RESOLVED LATER
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_expires (show other bugs)
Version: 2.0.54
Hardware: PC Linux
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords: MassUpdate
Depends on:
Blocks:
 
Reported: 2010-09-23 12:57 UTC by Francis Galiegue
Modified: 2018-11-07 21:09 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Francis Galiegue 2010-09-23 12:57:31 UTC
In a virtual host definition, I have the following:

----
ExpiresActive On

ExpiresDefault "now"
[...]
ExpiresByType application/x-javascript "access plus 1 month"

<Location "/cockpit/d">
    ExpiresDefault "now"
</Location>
----

The problem here is that the ExpiresByType directive has "sneaked" into the the <Location> section. The documentation says: "It overrides, for the specified MIME type only, any expiration date set by the ExpiresDefault  directive.". However, it doesn't explicitly state that this override occurs _in all contexts_ (Location, Directory).

This can be particularly painful by times, if we want to use mod_expires in quite complex Web applications where the expiration policy for the same MIME types can differ depending on the location (here, /js/t.js wants to be cached, but /cockpit/d/t.js doesn't). And in fact, I believed that specifying ExpiresDefault in a Location section would override all previous ExpiresDefault and ExpiresByType - it only overrides ExpiresDefault, though.

So, there are two ways of modifying the behaviour:

* either ExpiresDefault, when define inside a "subsection", _does_ override ExpiresByType as well;
* or implement an ExpiresActive reset, which could allow one to write:

<Location "/cockpit/d">
    ExpiresActive reset
    ExpiresDefault "now"
</Location>

with the following behavior:
  - if no ExpiresDefault or ExpiresByType exist in the subsection, obey the already existing ExpiresDefault and ExpiresByType directives;
  - if ExpiresDefault is present, obsoletes existing ExpiresByType directives (along with overriding any existing ExpiresDefault directive as it does currently).
Comment 1 William A. Rowe Jr. 2018-11-07 21:09:57 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.