Fix Apache's mod_expires Cache-Control issue #24
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Apaches's mod_expires is a widely used module to set HTTP caching headers. It allows you to set a default cache lifetime as well as lifetimes by mime_type.
When an application server has set a
Cache-Control
header, mod_expires ignores this and sets its own, resulting in duplicateCache-Control
headers and conflicting information. It does this unless the application server sets anExpires
header, in which case mod_expires does nothing. This is documented on the link above:Symfony automatically sets a
Cache-Control
header if a session exists. This patch ensures it's respected by mod_expires.Example 1
With the following Apache config:
The HTTP response headers are:
Without the patch
With the patch
Example 2
With the following Apache config:
Without the patch
With the patch