Cross-origin redirect timing opt-in

Category: Miscellaneous
Type: New or changed feature
Status: Proposed (Chrome Proposed)
Intent stage: None

Summary

Currently developers have no way to measure cross-origin redirects for navigations, even ones under their control, or ones that choose to opt-in to be measured. This feature enables servers to opt-in to have their redirects measured by the destination origin of the navigation.

Motivation

Enables developers to measure and optimize their cross-origin redirects, while ensuring that opt-in are secure and aligned with the developer's intention.

Standards & signals

Specification: https://github.com/whatwg/fetch/pull/1931
Firefox: No signal
Safari: Positive — No position filed as this is a minor behavior change. WebKit are explicitly supportive for WHATWG process pourposes.
Web developers: Positive — This was discussed at the WebPerfWG, and folks were supportive. Developers at Shopify are highly supportive of being able to measure and optimize redirects.
Tracking bug: https://issues.chromium.org/issues/521861828

Explainers: https://github.com/whatwg/html/pull/12513 https://github.com/whatwg/fetch/pull/1931

View on chromestatus.com