New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 895821 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature

Blocked on:
issue 912951



Sign in to add a comment

Persist Reporting/NEL policies across browser restarts

Project Member Reported by dcreager@chromium.org, Oct 16

Issue description

Right now, both Reporting and NEL only keep their per-origin policies in memory.  That means that every time Chrome restarts, all of the policies that we've received disappear.  This is especially a problem for NEL: if the user starts a fresh copy of Chrome and has a problem accessing a NEL-enabled origin, we won't have any NEL policy in memory that we can use to send a report to the server owner about those failures.
 
Owner: chlily@chromium.org
Cc: dcreager@chromium.org
The unsent and pending Reporting reports are also kept in memory. We should probably also persist those across restarts.

Relatedly, the ReportingCache currently handles both the Reporting policies and the reports. Should those perhaps be split up?
Blockedon: 912951

Sign in to add a comment