Howdy there, partner! Welcome on into the Stacker Saloon.
Saddle on up to a stool and spill the beans about your day, fire away with them questions, or let loose and give us the lowdown on your wild and woolly life. We're all ears, so don't hold back!
We're open round the clock, so mosey on in whenever you please!
A
, when we load pages, the path requested for SSR data will look like.../A/...json
. All the appropriate cache headers are set, e.g.no-store, no-cache
.B
, the browser/pwa (unless its a fresh navigation or reload) continues to request.../A/...json
on navigations. Even though.../A/...json
doesn't actually exist, ie its a 404 if visited directly, the service worker returns an empty response with status 200 ... so effectively all the data is stale.fetch('.../A/...json')
with default options in the browser console, then the service worker reports 404.X-Nextjs-Data: 1
header. If I remove the header, it 404's like it should.https://stacker.news
it'll return 200 for an arbitrary data request./_next/data/
routes are called, I think.