Contact emails
dcre...@chromium.org, julia...@chromium.org
Explainer
https://github.com/WICG/reporting/blob/master/EXPLAINER.md
Spec
https://wicg.github.io/reporting/
https://wicg.github.io/network-error-logging/
Note that for Reporting, this Intent to Ship only covers report delivery (§1-4), not the JavaScript ReportingObserver.
Tag review
https://github.com/w3ctag/design-reviews/issues/195
https://github.com/w3ctag/design-reviews/issues/24
Summary
Network Error Logging allows user agents to generate reports about the reliability of HTTPS requests to a particular origin. This data mimics what is available in server logs; however, by being collected client-side, it has visibility into outages that prevent users' requests from reaching the origin's serving infrastructure.
Reporting is the delivery mechanism that Network Error Logging uses to upload the reliability reports to collectors designated by the origin servers.
Link to “Intent to Implement”
https://groups.google.com/a/chromium.org/d/topic/blink-dev/V38Q47CxTIY/discussion
https://groups.google.com/a/chromium.org/d/topic/blink-dev/4VNY6Hf_ZB8/discussion
Is this feature supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
Yes
Debuggability
New Reporting tab in chrome://net-internals to show current state of Reporting/NEL caches [tracking bug]
Risks
Interoperability and Compatibility
Medium: This is a new feature, and Chrome is the only current implementation
Microsoft, Mozilla: Interested and supportive of the idea, but no immediate plans to implement.
Apple: No public signals.
Ergonomics
Other downstream specs are planning on using Reporting for delivery of reports
Activation
This is activated purely by headers in HTTPS responses from origins that want to have NEL reports collected. Users can opt out on a per-domain basis via the Background Sync permission.
Is this feature fully tested by web-platform-tests?
Reporting API tested here: https://github.com/w3c/web-platform-tests/tree/master/content-security-policy/reporting-api
NEL tests pending: https://github.com/WICG/network-error-logging/issues/70
Entry on the feature dashboard
https://www.chromestatus.com/features/5391249376804864
Note that for Reporting, this Intent to Ship only covers report delivery (§1-4), not the JavaScript ReportingObserver.
Summary
Network Error Logging allows user agents to generate reports about the reliability of HTTPS requests to a particular origin. This data mimics what is available in server logs; however, by being collected client-side, it has visibility into outages that prevent users' requests from reaching the origin's serving infrastructure.
Reporting is the delivery mechanism that Network Error Logging uses to upload the reliability reports to collectors designated by the origin servers.
Link to “Intent to Implement”
https://groups.google.com/a/chromium.org/d/topic/blink-dev/V38Q47CxTIY/discussion
https://groups.google.com/a/chromium.org/d/topic/blink-dev/4VNY6Hf_ZB8/discussion
Is this feature supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
Yes
Debuggability
New Reporting tab in chrome://net-internals to show current state of Reporting/NEL caches [tracking bug]
Risks
Interoperability and Compatibility
Medium: This is a new feature, and Chrome is the only current implementation
Microsoft, Mozilla: Interested and supportive of the idea, but no immediate plans to implement.
Apple: No public signals.
Ergonomics
Other downstream specs are planning on using Reporting for delivery of reports
Activation
This is activated purely by headers in HTTPS responses from origins that want to have NEL reports collected. Users can opt out on a per-domain basis via the Background Sync permission.
Is this feature fully tested by web-platform-tests?
Reporting API tested here: https://github.com/w3c/web-platform-tests/tree/master/content-security-policy/reporting-api
Entry on the feature dashboard
https://www.chromestatus.com/features/5391249376804864
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM0YUhDQ5Gquava3%3DRudd9rAP0%2BEhnU4HqnG%3Dte8u27nkjronA%40mail.gmail.com.
Hi, I have a couple security/privacy-related questions about this:- The Reporting spec has an open issue about dropping reports when switching networks. Was that ever resolved/implemented?
- Will Chrome allow users to clear the report cache as required by the Reporting spec? If so, how do they do that?
- To disable reporting using the Background Sync permission, do users block the origin receiving the reports or the origin that generated them?
( chrome://net-internals/#reporting on 68.0.3438.3 (Official Build) dev)
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/adaca9bc-d2f0-48b0-b687-be7839bf77e8%40chromium.org.
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/2a4afeb8-a57e-43c7-afe4-9ddc784ebe26%40chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/op.zlzs2do6rbppqq%40cicero2.linkoping.osa.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAK_TSXLYjRBga9fu%3DZMOQT7Xta8nbkvB30hLfiCXf4OUM91YnA%40mail.gmail.com.
Note that for Reporting, this Intent to Ship only covers report delivery (§1-4), not the JavaScript ReportingObserver.
Tag review
https://github.com/w3ctag/design-reviews/issues/195
https://github.com/w3ctag/design-reviews/issues/24
Summary
Network Error Logging allows user agents to generate reports about the reliability of HTTPS requests to a particular origin. This data mimics what is available in server logs; however, by being collected client-side, it has visibility into outages that prevent users' requests from reaching the origin's serving infrastructure.
Reporting is the delivery mechanism that Network Error Logging uses to upload the reliability reports to collectors designated by the origin servers.
Link to “Intent to Implement”
https://groups.google.com/a/chromium.org/d/topic/blink-dev/V38Q47CxTIY/discussion
https://groups.google.com/a/chromium.org/d/topic/blink-dev/4VNY6Hf_ZB8/discussion
Is this feature supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
Yes
Debuggability
New Reporting tab in chrome://net-internals to show current state of Reporting/NEL caches [tracking bug]
Risks
Interoperability and Compatibility
Medium: This is a new feature, and Chrome is the only current implementation
Microsoft, Mozilla: Interested and supportive of the idea, but no immediate plans to implement.
Apple: No public signals.
Ergonomics
Other downstream specs are planning on using Reporting for delivery of reports
Activation
This is activated purely by headers in HTTPS responses from origins that want to have NEL reports collected. Users can opt out of collecting and uploading reports about individual domains via the Background Sync permission.
Is this feature fully tested by web-platform-tests?
Reporting API tested here: https://github.com/w3c/web-platform-tests/tree/master/content-security-policy/reporting-api
NEL WPT tests out for review: network-error-logging#70, crrev#1106518
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM0YUhBVowjVTJgk1f7WBcfsX1mSb6xtbvXsrw1uDXnF6bqubg%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CACj%3DBEg55AKerRehG86STDeZcU%3DEOPW%2BcPCsKmEdsM%3DpsSf9Ag%40mail.gmail.com.