fix: return 404 instead of 200 for stale assets with adapter-cloudflare
#6879
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.
Hello, this is my first PR, so please bear with me.
After experiencing numerous problems when deploying new code to Cloudflare Pages with stale assets and cache settings (e.g. when Argo or Early Hints services were enabled), I discovered that requesting a non-existent asset from the
_app
directory always returned a status code of 200 and the contents of the static404.html
file if it existed, or nothing at all if it didn't. This caused a lot of issues for our users because they had to hard refresh our web page after a new deployment in order to invalidate the wrong cached content in their clients due to some bizarre Cloudflare Edge issues—this was needed even after purging the Cloudflare's cache.Instead of constructing a new response object and returning it as if the asset was there, I updated the Cloudflare adapter to return early if the asset was not found. I also included a check before caching the server response to avoid caching if the response was not ok.
Please don't delete this checklist! Before submitting the PR, please make sure you do the following:
Tests
pnpm test
and lint the project withpnpm lint
andpnpm check
Changesets
pnpm changeset
and following the prompts. All changesets should bepatch
until SvelteKit 1.0