This repository has been archived by the owner on Jan 12, 2023. It is now read-only.
Add surrogate-key response header #8
Comments
tripodsan
added a commit
that referenced
this issue
Jul 11, 2019
tripodsan
added a commit
that referenced
this issue
Jul 18, 2019
🎉 This issue has been resolved in version 1.2.4 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
3 similar comments
🎉 This issue has been resolved in version 1.2.4 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
🎉 This issue has been resolved in version 1.2.4 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
🎉 This issue has been resolved in version 1.2.4 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In order to be able to invalidate the cache when a github resource has changed, it would be helpful to use a surrogate-key. this is easier than compute all potential external URLs of a static resource.
Suggestion
Surrogate-Key
response header.The text was updated successfully, but these errors were encountered: