demo · v141
Purpose Header
Pick a prefetch trigger and watch what Chrome 141 actually sends versus what it sent before. Then paste your server's branch logic — the analyser tells you whether dropping the legacy Purpose: prefetch header will break your routing.
before Chrome 141
after Chrome 141
No evaluation yet.
migration cheat-sheet
// OLD (still works through 140):
if (req.headers["purpose"] === "prefetch") { /* serve cached / skip analytics */ }
// NEW (works in all versions, future-proof):
const sp = req.headers["sec-purpose"] || "";
if (sp.includes("prefetch") || sp.includes("prerender")) {
// serve cached / skip analytics
}
see also
- Stop sending Purpose: prefetch header — feature index
- ChromeStatus entry
- Spec