Intent to Prototype: Cross-origin redirect timing opt-in

21 views

Skip to first unread message

Yoav Weiss (@Shopify)

unread,

6:05 AM (3 hours ago) 6:05 AM

to blink-dev

Contact emails

yoav...@chromium.org

Explainer

This changes the behavior of Timing-Allow-Origin headers on navigation request redirect chains.
With this feature, cross-origin redirect chains where all the requests opt-in to the destination origin will expose non-zero values of `redirectCount`, `redirectStart` and `redirectEnd` to the destination document.

Specification

https://github.com/whatwg/html/pull/12513

https://github.com/whatwg/fetch/pull/1931

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.

Blink component

Blink>PerformanceAPIs>NavigationTiming

Web Feature ID

Missing feature - I haven't filed for one, as this seems like a minor fix to an existing API.

Motivation

Enable developers to measure and optimize their cross-origin redirects.

Initial public proposal

https://github.com/w3c/navigation-timing/issues/215

Goals for experimentation

None

Requires code in //chrome?

False