Crash, Burn, Report
summary
Browsers send structured failure reports as JSON via a Report-To header so misconnects, TLS errors, redirect loops, deprecations and CSP/XSS blocks are reported out-of-band; Chrome already implements Network Error Logging and deprecation/intervention/crash reports. A collector like Report URI ingests these POSTs (DMARC reports arrive as XML), lets teams see certificate expiry, redirect-loop, OOM and CSP payloads, and downsample with a sampling fraction. Real-world runs scan the top 1M sites (crawler.ninja), find expired certs, and can spike to ~2.4 GB of CSP data and ~35–40k reports/sec.
AI-written summary · about
chapters (18)
- 0:00Intro
- 0:45Who we are
- 1:07What is a browser
- 4:49Reporting API
- 8:14Network Error Logging
- 12:05Report to Header
- 15:44Crawler Ninja
- 16:24Crawler Ninja Demo
- 19:19Geolocation Report
- 22:09Deprecation Report
- 23:30Intervention Report
- 25:17Crash Report
- 26:56Content Security Policy
- 34:06Demo
- 38:43Demark
- 45:15Fake Email
- 49:21QA
- 52:00Report Your I
