expires tag
#14969
Merged
expires tag
#14969
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
timkelty
force-pushed
the
feature/cache-response-tag
branch
from
b56d22f
to
b28f4cb
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Adds a
expirestag for easier Twig access to\Craft::$app->getResponse()->setCacheHeaders.// Cache-Control: public, max-age=1814400 {% expires in 3 weeks %} // Cache-Control: public, max-age=30 {% expires on now|date_modify('+30 seconds') %} // Cache-Control: no-cache, no-store, must-revalidate {% expires %}Based on
4.10as it is useful for Cloud, but could be rebased to5.x.For
no-cache, I went with just{% expires %}vs{% expires now %}, as it seemed like withnow, we should support more relative times liketomorrow.