Topic: Why you need 'Network Error Logging' (NEL)

[Steffen]

I mentioned already NEL at https://www.apachelounge.com/viewtopic.php?t=8293

By adding a NEL response header to your website, you will receive reports from your visitors browsers, allowing you to accurately measure performance characteristics that will help you improve your website.

Introduction
Wouldn't it be great if every visitor to your site would take the time to notify you when they are experiencing connectivity issues? Wouldn't it be even better if they would also tell you exactly what caused the issue? Things like DNS lookup failures, connection timeouts, reset connections or dead links that result in 404 errors?

As most of these issues are not detectable server-side, since by definition the client might not have been able to successfully establish a connection with the server, getting client-side feedback would be extremely valuable!

Well..., stop fantasizing because this is now possible by adding just two response headers to your website. By adding the 'Report-To'- and 'NEL'-header you are instructing supporting user agents (browsers) to send you reports about connectivity issues. Aside from logging errors, NEL can also be used to log successful requests allowing you to determine rates of errors across different client populations.

Read More........ www.uriports.com/blog/network-error-logging/

With testing a new release, nowadays I set the NEL header.

[James Blond]

I see the point. But there is no description how to deal with the sent data, if I wanted to create that myself and not use uriports....

[Steffen]

You can customize the headers where to report.

Replace https://example.uriports.com/.... to your url at the different headers as described at https://www.uriports.com/getting-started .

At https://www.uriports.com/getting-started you can click button Open Official Documentation. For the Reporting API you go to https://www.w3.org/TR/reporting/ , first
impression for me that it quite complex.


When you want DMARC and/or SMPT TLS reporting: change mail-to to yours in the DNS records (I do that for some domains). Your mailservers must support DMARC and/or MTA-STS