New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: ensure Cache-Control
is specified in 304 response
#971
Conversation
…by some CDNs to cache properly
Codecov Report
@@ Coverage Diff @@
## master #971 +/- ##
==========================================
+ Coverage 66.88% 66.90% +0.01%
==========================================
Files 95 95
Lines 10036 10040 +4
Branches 1573 1623 +50
==========================================
+ Hits 6713 6717 +4
Misses 3319 3319
Partials 4 4
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
## [1.0.7](v1.0.6...v1.0.7) (2022-01-12) ### Bug Fixes * ensure `Cache-Control` is specified in 304 response as required by some CDNs to cache properly ([#971](#971)) ([a0fd2fe](a0fd2fe))
🎉 This PR is included in version 1.0.7 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Fixes caching issue with certain CDNs (e.g. Cloudflare) where intermediate caching will only be performed if the
304 CACHE OK
response also includes theCache-Control
headers.Cloudflare will perform intermediate caching when the following page rules are applied for
/v1/extended/*
: