4 ms·
TIL about Network Error Logging[1], which is having browsers send you reports that your DNS isn't resolving, your load balancer is timing out (HTTP / TCP errors
by Androider 6y ago
TIL about Network Error Logging[1], which is having browsers send you reports that your DNS isn't resolving, your load balancer is timing out (HTTP / TCP errors in general), or your TLS certificate is invalid. Basically all types of issues that don't end up in your own application server logs.
Report URI should lead with this (it's not even mentioned on the front page)! It's super useful for every site, I can't think why anyone wouldn't want this. CSP monitoring on the other hand, which seems to be their focus, is a much harder sell, a pain to setup and maintain, and a bit questionable value in my opinion.
[1] https://report-uri.com/products/network_error_logging https://report-uri.com/products/network_error_logging
- parliament32 6y agoThis is the actual tech, rather than a commercial solution: https://w3c.github.io/network-error-logging/#introduction https://w3c.github.io/network-error-logging/#introduction https://developer.mozilla.org/en-US/docs/Web/HTTP/Network_Error_Logging https://developer.mozilla.org/en-US/docs/Web/HTTP/Network_Er...
- Androider 6y agoReport URI is run by Scott and was featured in the article. By definition you have to run such a service entirely separate from your own infrastructure: you should use a different CA than your other site(s), a different domain name for sure, preferably a different infrastructure host etc. It makes a lot of sense to use something like the Report URI service for it.
- nitrogen 6y agoThis looks incredibly useful! It'll also probably tell you who is using Pi-hole though.