Support signed exchange subresource prefetching and loading by extending the HTTP link header.
An Origin Trial for Subresource prefetching+loading via Signed HTTP Exchange started in Chrome 78 and is scheduled to end in Chrome 82. We have received some feedback from developers like this. But getting adoption of this feature takes time because it requires both article publisher’s adoption and article aggregator’s adoption. So we intend to extend the Origin Trial until Chrome 86.
Link to “Intent to Implement” blink-dev discussion
Goals for experimentation
The main goal is to measure the performance benefit of alternative subresource signed exchange prefetch. And also, this feature requires participation of both content publishers and distributors. So we would like to know whether this API design and mechanism works or not.
M78 - M86
Any risks when the experiment finishes?
After the OriginTrial expires, Chrome will not prefetch the alternative subresource signed exchanges, but will prefetch the original subresources written in the inner link header.
Ongoing technical constraints
DevTools shows the information about signed exchange subresource prefetching and loading in the Network tab.
Will this feature be supported on all five Blink platforms supported by Origin Trials (Windows, Mac, Linux, Chrome OS, and Android)?
Link to entry on the feature dashboard
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+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CADk0S-XwM8ddyiAYsXqW4N1ZsiaBv9RjhdM9212tjJ%2BNxCLR_w%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CADk0S-WxcSfbxbdsJ7OzmDr7Xq6Bk908Vuv7DmfjdgJMTM3heA%40mail.gmail.com.