Cache Errors rendering site unavailable
Occasionally, with no intervention - our apps will cache incorrectly causing the app to be unavailable on Pages. We mostly see this as pages that should be returning javascript return the homepage instead. To get around it, we usually run a "Retry deployment" which to my understanding invalidates the existing cache on the affected pages.
I am certain this is not a oneoff, this has happened twice to the primary subject of this report but also my personal website which does not use Next.js.
We are
playlessgames.pages.dev
My account ID is eedfd4b5dcbc4abc94e0eda2d3e14b92
Details, including a live reproduction from my personal website is in the thread.7 Replies
My personal website is made with Astro and uses "Server Islands" which are just individually SSR'd components. You can see something is missing here, usually the gap after the location tag is filled in by a request Astro makes to
/_server-islands/ComponentName (in my case, ComponentName is Distance).
However, the request made by Astro and navigating to that page manually gives you https://a2ad6104.web-1mb.pages.dev/_server-islands/Distance the full website?
(web-1mb.pages.dev belongs to my personal account, c5541e8801de162b20b23687ef90296e)Dj I. // DeJayDev
Software Engineer - I help make dreams come true.
Astro's signed(?) version of the request
Expected behavior
You can also still see this in production on the app I still care about:
https://lessgames.com/_next/static/chunks/pages/_app-3dcf316cd920dee4.js
This app has had it's full cache cleared (using the Dashboard button) and still serves HTML on what should be a JavaScript response. One would expect a not found page, like https://lessgames.com/pagethatdoesntexist
Firefox (appears to) use that NS_ERROR_CORRUPTED_CONTENT when the MIME type of the response doesn't match what Firefox expected to see (javascript). Whatevers happens here renders my app unusable, and because it's not technically going offline my current monitoring doesn't identify the issue.