-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Support immutable cache headers for _astro assets #9125
Conversation
🦋 Changeset detectedLatest commit: ec4d59e The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
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.
Seems great!
Co-authored-by: Nate Moore <natemoo-re@users.noreply.github.com>
Out of curiosity, could this also be done for other adapters with their respective folders? (ie. astro and vercel for the vercel adapter) |
@florian-lefebvre it can be yes, the Vercel adapter already has it. |
Oh ok, looking at the issue I assumed it was concerning every adapter. It may be worth saying it on adapters docs, because I suspect many people (me included) add those headers to vercel/netlify config but if it's done by default, that's even better! |
@florian-lefebvre Yeah, Astro core isn't responsible for serving static assets. I agree on the docs, I'll add that to this PR. |
Waiting on docs review before merging. |
Co-authored-by: Sarah Rainsberger <sarah@rainsberger.ca>
Co-authored-by: Sarah Rainsberger <sarah@rainsberger.ca>
Changes
_astro
in the Node adapter.Testing
_astro
is given the header.Docs
N/A, bug fix