Signed HTTP Exchanges (SXG)
- OTHERPart of the Web Packaging spec, Signed HTTP Exchanges allow a different origin server to provide a resource, and this will be treated as if it came from the original server. This can be use with AMP CDNs, for example, to allow the original URL to be displayed in the URL bar.
Chrome
- 4 - 70: Not supported
- 71 - 72: Partial support
- 73 - 110: Supported
- 111: Supported
- 112 - 114: Supported
Edge
- 12 - 18: Not supported
- 79 - 110: Supported
- 111: Supported
Safari
- 3.1 - 16.2: Not supported
- 16.3: Not supported
- 16.4 - TP: Not supported
Firefox
- 2 - 110: Not supported
- 111: Not supported
- 112 - 113: Not supported
Opera
- 9 - 63: Not supported
- 64 - 94: Supported
- 95: Supported
IE
- 5.5 - 10: Not supported
- 11: Not supported
Chrome for Android
- 111: Supported
Safari on iOS
- 3.2 - 16.2: Not supported
- 16.3: Not supported
- 16.4: Not supported
Samsung Internet
- 4 - 10.1: Not supported
- 11.1 - 19.0: Supported
- 20: Supported
Opera Mini
- all: Not supported
Opera Mobile
- 10 - 12.1: Not supported
- 73: Supported
UC Browser for Android
- 13.4: Supported
Android Browser
- 2.1 - 4.4.4: Not supported
- 111: Supported
Firefox for Android
- 110: Not supported
QQ Browser
- 13.1: Supported
Baidu Browser
- 13.18: Supported
KaiOS Browser
- 2.5: Not supported
- 3: Not supported
Note this requires the page to be delivered signed by a certificate with the CanSignHttpExchanges extension.
- Resources:
- Developer Preview of better AMP URLs in Google Search
- Microsoft Edge Platform Status - Supported
- Signed HTTP Exchanges on Google's Web Development site
- GitHub home page for Web Packaging
- Signed-Exchange: Solving the AMP URLs Display Problem
- Mozilla's Position about Signed HTTP Exchanges (harmful)
- Chrome platform status - Shipped