Signed HTTP Exchanges (SXG)

- OTHER

Part 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.

IE

  1. 5.5 - 10
  2. 11

Edge

  1. 12 - 18
  2. 79 - 81
  3. 83

Firefox

  1. 2 - 75
  2. 76
  3. 77 - 78

Chrome

  1. 4 - 70
  2. 71 - 72
  3. 73 - 81
  4. 83
  5. 84 - 86

Safari

  1. 3.1 - 13
  2. 13.1
  3. TP

Opera

  1. 9 - 63
  2. 64 - 67
  3. 68

iOS Safari

  1. 3.2 - 13.3
  2. 13.4

Opera Mini

  1. all

Android Browser

  1. 2.1 - 4.4.4
  2. 81

Blackberry Browser

  1. 7
  2. 10

Opera Mobile

  1. 10 - 12.1
  2. 46

Chrome for Android

  1. 81

Firefox for Android

  1. 68

IE Mobile

  1. 10
  2. 11

UC Browser for Android

  1. 12.12

Samsung Internet

  1. 4 - 10.1
  2. 11.1

QQ Browser

  1. 10.4

Baidu Browser

  1. 7.12

KaiOS Browser

  1. 2.5

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