Intent to Experiment: Subresource prefetching+loading via Signed HTTP Exchange

[Tsuyoshi Horo]

Contact emails

ho...@chromium.org

Spec

https://github.com/WICG/webpackage/issues/347

Summary

Support signed exchange subresource prefetching and loading by extending the HTTP link header.

Link to “Intent to Implement” blink-dev discussion

https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/zdvJLcditVA

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. 

Experimental timeline

M78 - M82(tentative)

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 inner link header.

Ongoing technical constraints

None

Debuggability

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)?

Yes

Link to entry on the feature dashboard

https://www.chromestatus.com/features/5126805474246656

[Yoav Weiss]

LGTM

This experiment seems like a reasonable way to create a privacy-preserving replacement to prerender, by preloading resources that the prefetched page relies on.

An OT here seems like the perfect tool to prove that this actually works! :)

--
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-Unv%2BXckHZzr7%2B-_w8w8N-1JXTBUXteqOnoZvO03DfMTA%40mail.gmail.com.