Lines Matching full:reports

3 Reporting is a central mechanism for sending out-of-band error reports
29   other parts of `//net` and other components: queueing reports,
33       API, such as the maximum number of reports and endpoints to queue, the
34       time interval between delivery attempts, whether or not to persist reports
41         * The *`ReportingCache`* stores undelivered reports and endpoint
48         * The *`ReportingDeliveryAgent`* reads reports from the cache, decides
53               reports: accepts a URL and JSON from the `DeliveryAgent`, creates
63           and removes reports that have remained undelivered for too long, or
67           and removes browsing data (reports and endpoints) of selected types
71           to check permissions for queueing/sending reports and setting/using
89 * A reporting source, used only by V1 reports, is a `base::UnguessableToken`
94   documents or workers, it tracks configurations and reports using this source
97   is destroyed, for instance.) This will cause any outstanding reports for that
102 * In the network service, a `network::NetworkContext` queues reports by getting
108     * It queues reports via the `NetworkContext` using a
111       CSP Violation, and Permissions Policy Violation reports.
114   for queueing reports and setting/using clients based on whether cookie access
115   is allowed, and checks permissions for sending reports using a
121   embedders to collect and send reports before having received a header in an
125       Logging reports [in the Cronet Java tests][4].
131 required for Network Error Logging, as those reports are not associated with
134 All V0 reports destined for the same endpoint group may be bundled together for
140 documents and workers, since other resources do not currently generate reports.
145 V1 reports from the same source may be bundled together in a single delivery,
146 but must be delivered separtely from other reports, even those coming from a
152 header. Until we can, it is possible for reports to be sent to endpoints
153 configured with either header. NEL reports can only go to those endpoint groups
161 * All reports which can be associated with a specific source (currently all
162   reports except for NEL, which requires origin-scoped V0 configuration) must be