This repository has been archived by the owner on Mar 9, 2021. It is now read-only.
Expires headers and ETag removal #7
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
We had actually decided a couple days ago that we wanted to add these back in. So this PR is well timed. Thanks! |
QWp6t
added a commit
that referenced
this pull request
Jul 16, 2014
Expires headers and ETag removal
|
Nice :) |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
For users who don't want to use W3 Total Cache, it would be nice to have expires headers and etag removal kept in the .htaccess file. And even for users who do have a caching plugin, is there any downside to keeping these rules in the .htaccess?
Just my 2 cents :)