Contact emails
steven...@microsoft.com

Explainer
None


Specification
None


Summary

Now that prefetches and prerenders are utilizing the Sec-Purpose header for 
prefetches and prerenders, we will move to remove the legacy Purpose: 
"prefetch" header that is still currently passed. This will be behind a feature 
flag/ kill switch to prevent compat issues.



Blink component
Blink>Loader>Preload


Motivation

Each browser uses non-standardized header name that is not aligned with CORS 
spec (Mozilla's x-moz, chrome's purpose, and Safari doesn't support prefetch 
yet). As part of standardizing the header names, Sec-Purpose: "prefetch" and 
Sec-Purpose: "prefetch;prerender" is used. This is to remove current legacy 
code that still adds the Purpose: "prefetch" header to maintain the 
standardized name going into the future.



Initial public proposal
https://fetch.spec.whatwg.org/#sec-purpose-header


TAG review
None


TAG review status
Pending


Risks




Interoperability and Compatibility

As commented at notes on Firefox and Safari, each browser uses non-standardized 
header name that is not aligned with CORS spec. This change will introduce 
better interoperability and compatibility for a long term.


Gecko: No signal

WebKit: No signal

Web developers: No signals

Other signals:


WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that it 
has potentially high risk for Android WebView-based applications?

None




Debuggability

None



Is this feature fully tested by web-platform-tests?
Yes
https://wpt.fyi/results/preload/prefetch-headers.https.html?label=experimental&label=master&aligned



Flag name on about://flags
None


Finch feature name
RemovePurposeHeaderForPrefetch


Requires code in //chrome?
False


Estimated milestones

No milestones specified



Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5088012836536320?gate=5078009555714048


This intent message was generated by Chrome Platform Status.

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to blink-dev+unsubscr...@chromium.org.
To view this discussion visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6836470b.2b0a0220.33c819.0963.GAE%40google.com.

Reply via email to