Intent to Implement: Signed Exchange Reporting for distributors
Tsuyoshi Horo
Contact emails
Explainer
https://docs.google.com/document/d/1Io-MJ1PUqPazZIzDdV2s7oTPGLJZGt15Pbx1ge3JYT4/edit?usp=sharing
Summary
Signed Exchange Reporting for distributors extends the Network Error Logging to enable the distributors of signed exchanges to investigate the signed exchange loading errors such as certificate verification errors.
Motivation
Signed Exchange feature enables content publishers to sign their contents using their own private keys. User Agents (UAs) can trust the signed contents as if the contents are served from the publisher’s origins even if they are served from other distributors’ origins. Even if there is no network errors, UA may fail to load the signed content (example: the signature of the content has expired). This case is not covered by the Network Error Logging feature now. Both publishers and distributors can’t recognize the errors in the user’s environment.
Interoperability risk
Edge: No signals
Firefox: No signals
Safari: No signals
Web / Framework developers: No signals
Compatibility risk
This feature introduces a new phase type "sxg", so the existing NEL endpoints can detect that this is a new type of report.
Ongoing technical constraints
None
Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
Yes
OWP launch tracking bug
Link to entry on the Chrome Platform Status
https://www.chromestatus.com/features/5687904902840320
Requesting approval to ship?
No