BASELINE: Update Chromium to 86.0.4240.124

Change-Id: Ide0ff151e94cd665ae6521a446995d34a9d1d644
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>

2 files changed, 36 insertions, 0 deletions

diff --git a/chromium/net/network_error_logging/OWNERS b/chromium/net/network_error_logging/OWNERS
index 46f7dc92b25..4e378e9fde3 100644
--- a/chromium/net/network_error_logging/OWNERS
+++ b/chromium/net/network_error_logging/OWNERS
@@ -1,3 +1,7 @@
 chlily@chromium.org
 
+# This is the component for the Network Error Logging API.
+# For chrome://net-export and NetLogs, see Internals>Network>Logging.
+# For network errors in general, see Internals>Network.
+
 # COMPONENT: Internals>Network>ReportingAndNEL
diff --git a/chromium/net/network_error_logging/README.md b/chromium/net/network_error_logging/README.md
new file mode 100644
index 00000000000..6494401c274
--- /dev/null
+++ b/chromium/net/network_error_logging/README.md
@@ -0,0 +1,32 @@
+# Network Error Logging (NEL)
+
+Network Error Logging (NEL) provides out-of-band reporting of network errors
+via the Reporting API (see `//net/reporting`). Site operators can specify a
+NEL policy that defines the Reporting endpoint(s) on which they wish to receive
+reports about client-side errors encountered while connecting to the site. The
+draft spec can be found [here](https://w3c.github.io/network-error-logging/).
+
+This directory contains the core implementation of NEL.
+
+## Implementation overview
+
+Most of the action takes place in
+[`NetworkErrorLoggingService`](https://source.chromium.org/chromium/chromium/src/+/master:net/network_error_logging/network_error_logging_service.h;l=42;drc=a9e9d6cbb3e5920f9207118cf9501ff0745bb536),
+which handles receiving/processing `NEL:` response headers and
+generating/queueing reports about network requests. The
+`NetworkErrorLoggingService` is owned by the `URLRequestContext`.
+
+Information about network requests comes directly from
+[`HttpNetworkTransaction`](https://source.chromium.org/chromium/chromium/src/+/master:net/http/http_network_transaction.cc;l=1364;drc=a9e9d6cbb3e5920f9207118cf9501ff0745bb536),
+which informs `NetworkErrorLoggingService` of the details of the request such
+as the remote IP address and outcome (a `net::Error` code).
+
+The `NetworkErrorLoggingService` finds a NEL policy applicable to the request
+(previously set by a `NEL` header), and if one exists, potentially queues a
+NEL report to be uploaded out-of-band to the policy's specified Reporting
+endpoint via the
+[`ReportingService`](https://source.chromium.org/chromium/chromium/src/+/master:net/reporting/reporting_service.h;l=56;drc=c3305c04ac6800d488bfc8b2f3249fd13186984a).
+
+Received NEL policies are persisted to disk by a `PersistentNelStore`, whose
+main implementation is the
+[`SqlitePersistentReportingAndNelStore`](https://source.chromium.org/chromium/chromium/src/+/master:net/extras/sqlite/sqlite_persistent_reporting_and_nel_store.h;l=30;drc=456596a0b27623349d38e49d0e9812b24d47d5d8).