*Contact emails* [email protected] *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 <https://github.https://github.com/whatwg/fetch/pull/1931com/whatwg/html/pull/12513> *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 <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3EPerformanceAPIs%3ENavigationTiming%22> *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 *Tracking bug* https://issues.chromium.org/issues/521861828 *Estimated milestones* No milestones specified *Link to entry on the Chrome Platform Status* https://chromestatus.com/feature/5078310347472896?gate=5095595409801216 This intent message was generated by Chrome Platform Status <https://chromestatus.com/>. -- 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 [email protected]. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOmohS%2BmvvuuG%3D0Jww9xDpDZVsgn90p-VHUjX-exx2SnU8Zf%3Dg%40mail.gmail.com.
