Lines Matching full:reporting

1 # Reporting  chapter
3 Reporting is a central mechanism for sending out-of-band error reports
9  * The original API implemented in Chrome (Reporting V0) can be found at
10      [https://www.w3.org/TR/2018/WD-reporting-1-20180925/].
11  * The newer API is split into two parts. Document and worker-level reporting
12      (Reporting V1) is specified in the [draft reporting spec]
13      (https://w3c.github.io/reporting/), while Network-level reporting is
14      specified in the [draft network reporting spec]
15      (https://w3c.github.io/reporting/network-reporting.html).
19 ## Reporting in Chromium
21 Reporting is implemented as part of the network stack in Chromium, such
32     * A *`ReportingPolicy`* specifies a number of parameters for the Reporting
39       contains the inner workings of Reporting, spread across several classes:
43           per reporting source in the V1 spec).
46           `Reporting-Endpoints' headers and updates the cache accordingly.
82 * `Reporting-Endpoints:` headers are initially parsed by
85   response until a reporting source can be associated with it, and is then
89 * A reporting source, used only by V1 reports, is a `base::UnguessableToken`
90   associated with the document (or worker eventually) which configures reporting
91   using a `Reporting-Endpoints:` header. This same token must be passed into
105 * The JavaScript [ReportingObserver](https://w3c.github.io/reporting/#observers)
127 ## Differences between V0 and V1 reporting
129 The original V0 reporting API included support for the `Report-To` header only,
137 V1 reporting drops the `Report-To` header in favor of `Reporting-Endpoints`,
141 Chrome ignores any `Reporting-Endpoints` headers on those responses.) The V1 API
149 ## Supporting both V0 and V1 reporting in the same codebase
163   queued with that source's reporting source token.