logo
Apache Lounge
Webmasters

 

About Forum Index Downloads Search Register Log in  RSS Apache Lounge  


Keep Server Online

If you find the Apache Lounge, the downloads and overall help useful, please express your satisfaction with a donation.

or

Bitcoin

A donation makes a contribution towards the costs, the time and effort that's going in this site and building.

Thank You! Steffen

Your donations will help to keep this site alive and well, and continuing building binaries. Apache Lounge is not sponsored.



Post new topic   Forum Index -> Webmaster Tools & Utilities View previous topic :: View next topic
Reply to topic   Topic: Why you need 'Network Error Logging' (NEL)
Author
Steffen
Moderator


Joined: 15 Oct 2005
Posts: 2807
Location: Hilversum, NL, EU

PostPosted: Sat 04 Jan '20 21:05    Post subject: Why you need 'Network Error Logging' (NEL) Reply with quote

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.
Back to top
James Blond
Moderator


Joined: 19 Jan 2006
Posts: 6714
Location: Germany, Next to Hamburg

PostPosted: Fri 10 Jan '20 10:28    Post subject: Reply with quote

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....
Back to top
Steffen
Moderator


Joined: 15 Oct 2005
Posts: 2807
Location: Hilversum, NL, EU

PostPosted: Fri 10 Jan '20 11:45    Post subject: Reply with quote

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
Back to top


Reply to topic   Topic: Why you need 'Network Error Logging' (NEL) View previous topic :: View next topic
Post new topic   Forum Index -> Webmaster Tools & Utilities