1145235 - Implement Network Error Logging spec

Status: ASSIGNED

(Core :: Networking, task, P3)

Description

[Marcos Caceres [:marcosc]]

The spec "defines a mechanism that enables developers to declare a network error reporting policy for a web application. A user agent can use this policy to report encountered network errors that prevented it from successfully fetching requested resources."

Comment 1

[Firefox Bug Husbandry Bot]

Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258

Comment 2

[Firefox Bug Husbandry Bot]

Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258

Comment 3

[Logan Rosen [:Logan]]

This was implemented in Chrome 69: https://www.chromestatus.com/feature/5391249376804864

Do we have plans to tackle this for Firefox? It's a very useful feature for website owners to find out if their users are experiencing network or other issues while accessing their sites.

Comment 4

[Dragana Damjanovic [:dragana]]

(In reply to Logan Rosen [:Logan] from comment #3)

This was implemented in Chrome 69: https://www.chromestatus.com/feature/5391249376804864

Do we have plans to tackle this for Firefox? It's a very useful feature for website owners to find out if their users are experiencing network or other issues while accessing their sites.

How widely is it used? It was put in "backlog" because it was not widely used. Has this changed?

Comment 5

[Logan Rosen [:Logan]]

We're looking into enabling a NEL policy for LinkedIn due to reporting being enabled by default in Chrome - we think we can get some really useful data about the types of issues members may be experiencing while accessing our products. I'd love to see our members who use Firefox being able to contribute reports as well.

On top of this, Catchpoint, a popular external monitoring solution, recently announced a Real User Monitoring product that accepts NEL reports, so this is definitely getting more adoption: http://blog.catchpoint.com/2018/09/27/identify-website-availability-issues-with-real-user-monitoring/

Comment 6

[lol768]

The University of Warwick is using this in production as part of a wider strategy to help track fetch errors (particularly those that occur during online assessments). Wider browser support would be welcomed.

I've found that documentation on this feature (and the reporting API itself) is thin on the ground. So, I've written up some docs to cover NEL on MDN:

• https://wiki.developer.mozilla.org/en-US/docs/Web/HTTP/Network_Error_Logging

And added some compat data:

• https://github.com/mdn/browser-compat-data/pull/5994

Comment 7

[Neil Shah-Quinn]

Wikimedia is now using NEL on a large scale as well. For example, it feeds the "user-reported connectivity errors" metric listed on our systems status page. The behind-the-scenes details are documented at wikitech.wikimedia.org/wiki/Network_Error_Logging.

Comment 8

[Simon Friedberger (:simonf)]

Attachment: nel data review request.txt

Comment 9

[Simon Friedberger (:simonf)]

:chutten could you please have a look at the attached data review request? We need to define the categories of the collected data so decide if or how we want to support this.

Comment 10

[Chris H-C :chutten]

I'm a little confused, is this data being collected and sent to Mozilla's servers about the use of Network Error Logging? Or is this data request about the mechanism of Network Error Logging itself?

If the latter, please engage directly with Privacy and Trust for reviewing the addition of a new system of data collection and reporting.

Comment 11

[Chris H-C :chutten]

Comment on attachment 9357803 [details]
nel data review request.txt

Upon conversation this is indeed a "data request about the mechanism of Network Error Logging itself".

Comment 12

[Simon Friedberger (:simonf)]

It is indeed the latter.

Comment 13

[Valentin Gosu [:valentin] (he/him)]

Attachment: Bug 1145235 - Add nsIIOService.originAttributesForNetworkState r=#necko

Comment 14

[Valentin Gosu [:valentin] (he/him)]

Attachment: Bug 1145235 - Implement (subset of) NEL spec r=#necko

Comment 15

[Valentin Gosu [:valentin] (he/him)]

Attachment: Bug 1145235 - Expose last status on nsIHttpChannelInternal r=#necko

Comment 16

[Valentin Gosu [:valentin] (he/him)]

Attachment: Bug 1145235 - Add triggeringPrincipal override to RequestInit r=#necko

This allows code with Chrome priviledges to use the fetch API
to specify a triggering principal instead of needing to use
XMLHttpRequest.
The triggeringPrincipal is only used when the fetch principal
is already the systemPrincipal.

Comment 17

[Phabricator Automation]

Comment on attachment 9400724 [details]
Bug 1145235 - Add nsIIOService.originAttributesForNetworkState r=#necko

Revision D209819 was moved to bug 1911759. Setting attachment 9400724 [details] to obsolete.

Comment 18

[Phabricator Automation]

Comment on attachment 9401354 [details]
Bug 1145235 - Expose last status on nsIHttpChannelInternal r=#necko

Revision D210145 was moved to bug 1911759. Setting attachment 9401354 [details] to obsolete.

Comment 19

[Phabricator Automation]

Comment on attachment 9400725 [details]
Bug 1145235 - Implement (subset of) NEL spec r=#necko

Revision D209820 was moved to bug 1911759. Setting attachment 9400725 [details] to obsolete.

Comment 20

[Phabricator Automation]

Comment on attachment 9406974 [details]
Bug 1145235 - Add triggeringPrincipal override to RequestInit r=#necko

Revision D213418 was moved to bug 1911759. Setting attachment 9406974 [details] to obsolete.