Crash, Burn, Report
summary
Browsers send out-of-band failure reports via the Reporting API by a simple response header like report-to header (JSON) with a cached max-age, so Chrome will POST diagnostics later even if DNS, TCP or TLS prevents a page load. Subscribe to Network Error Logging (NEL) to get DNS/TCP/certificate/redirect-loop errors as a JSON payload, enable deprecation and intervention reports for APIs like geolocation, and use SPF/DKIM/DMARC for email—DMARC arrives as daily XML reports from providers (e.g. Gmail).
AI-written summary · about
chapters (10)
- 0:00Start
- 0:10Crash, Burn, Report
- 6:30Report-To
- 13:30NEL Reporting
- 19:25BOHEMIA
- 25:16Deprecation Report
- 27:32Intervention Report
- 29:25Crash Report
- 33:13Browser Reporting Capabilities
- 43:31DMARC
related talks
01h 02mCrash, Burn, Report
59mCrash, Burn, Report
20mNetwork Error Logging: Client side measurement of end to end web service reliability
41mhttps://*every site here*
27mCrash Course in CrUX
28mLet's Save The Internet
30mThe Chrome DevTools Performance Panel
56mWhat We’ve Learned From Billions of Security Reports
