Chrome has support for signed exchanges, which allows caching of content by a third party, but browser can show URL of original site as the content was signed by that site. https://developers.google.com/web/updates/2018/11/signed-exchanges
This enables things like search engines to speed up user experiences using privacy preserving prefetch.
I could not see signed exchanges (or Web Packaging in general) listed.
@Fyrd It seems sensible to split the layers described in https://github.com/Fyrd/caniuse/issues/4689 into 3 separate issues. In which case this issue tracks impl. of HTTP Signed Exchanges, and we'll have to open issues for the other 2 spec layers of the Webpackage API.
Edit:
Loading Signed Exchanges tracked in: https://github.com/Fyrd/caniuse/issues/4929
Bundled HTTP Exchanes tracked in: https://github.com/Fyrd/caniuse/issues/4930
Specification (Signed HTTP Exchanges) :
https://tools.ietf.org/html/draft-yasskin-http-origin-signed-responses
Chrome status:
https://www.chromestatus.com/feature/5745285984681984
Most helpful comment
@Fyrd It seems sensible to split the layers described in https://github.com/Fyrd/caniuse/issues/4689 into 3 separate issues. In which case this issue tracks impl. of HTTP Signed Exchanges, and we'll have to open issues for the other 2 spec layers of the Webpackage API.
Edit:
Loading Signed Exchanges tracked in: https://github.com/Fyrd/caniuse/issues/4929
Bundled HTTP Exchanes tracked in: https://github.com/Fyrd/caniuse/issues/4930