fix(frontend): keep the service worker off /feedback/, and let the feedback site answer HEAD (#535) #551
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/pwa-feedback-fallback"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Reported by the owner: opening any page of the design-review feedback site at
questboard-dev.rhoving.com/feedback/…redirected to the Quest Board dashboard.Cause. The installed app's service worker (
navigateFallback: "/index.html", scope/) answers every navigation on its origin with the app shell unless the path is denylisted, and only/api/,/auth/and/public/were. A browser that had visited the dev app therefore loaded/feedback/playersas Quest Board, whose router sends unknown paths to/dashboard. Requests without a worker (curl, a fresh browser, the friend's phone) saw the real site, which is why the server-side checks all passed.Fix.
/feedback(and anything under it) joins thenavigateFallbackDenylistand gets aNetworkOnlyruntime route so its pages and API are never cached either. The built worker was checked to contain the new entry. The comment names the general rule: any non-app path served on this hostname needs the same treatment. Browsers holding the old worker pick up the new one on their next visit (autoUpdate,skipWaiting,clientsClaim) and are right after one reload.Also. The feedback site's page routes now accept
HEADas well asGET; link previewers and uptime checks probe withHEAD, and a 405 there reads as a dead link. Already deployed on the dev box.CHANGELOG: one
**Fixed**entry.🤖 Generated with Claude Code