-
Notifications
You must be signed in to change notification settings - Fork 493
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
Cache Control for 404 response #1001
Comments
Hi. Can you please share nuxt/nitro versions? |
It's latest 2.2.3 |
@pi0 here is example, https://test-docus.vercel.app/_nuxt/test.css. As you see cache-control exists here, while response status is 404
|
Hi. I'm not sure if the deployment (cannot see source of open it anymore) were depending on cache headers generated by vercel edge or nitro so please feel free to open new issue with reproduction if facing similar issues. |
Environment
Cloudflare Workers (i think all envs have same logic)
Reproduction
Try to access localhost:3000/_nuxt/test.css and see Cache Control headers.
Describe the bug
I think nitro shouldnt cache 404's errors by default or atleast with different rules. For now we are facing issue when user visited page after deploy and 404 response was cached in browser.
Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered: