Intent to Prototype: Speculation Rules: Referrer-provided prefetch proxies

[Chromestatus]

Contact emails

elbu...@google.com

Explainer

https://github.com/WICG/nav-speculation/blob/main/referrer_provided_prefetch_proxies_draft.md

Specification

No information provided

Summary

This feature extends speculation rules with a new requirement that allows sites to set a referrer-provided prefetch proxy for their documents' cross-origin prefetches. This allows sites to speed up cross-origin/site navigations using a proxy of their choice.

Blink component

Internals>Preload>PrefetchProxy

Web Feature ID

speculation-rules

Motivation

The Speculative Loading spec asks browsers to provide IP-anonymizing proxies to satisfy the "anonymous-client-ip-when-cross-origin" requirement for speculation rules. Privacy concerns limit the use of browser-provided prefetch proxies. Only sites that are 1P to the browser and prefetch proxy can straightforwardly use the requirement above. For 3P sites, the proxy is only usable when the user has opted-in to an additional privacy setting. In the referrer-provided prefetch proxy architecture, the website initiating the prefetch operates its own privacy-preserving proxy server and specifies it in the page’s speculation rules script. This aligns the proxy trust model, avoids introducing a third-party service, and shifts the operational cost to the party that directly benefits from faster navigation.

Initial public proposal

https://github.com/WICG/nav-speculation/issues/368

Goals for experimentation

None

Requires code in //chrome?

False

Tracking bug

https://g-issues.chromium.org/issues/510022186

Launch bug

https://launch.corp.google.com/launch/4466508

Estimated milestones

No milestones specified

Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5087319398940672?gate=5379797813428224

This intent message was generated by Chrome Platform Status.