Skip to content

Investigate report-uri management workflows #32

Open
@igrigorik

Description

@igrigorik

Current draft specifies two report-uri "management workflows":

  • The report-uri can immediately unregister itself from NEL policy by returning a 410 Gone
  • The user agent may remove report-uri from NEL policy if it fails to deliver the report to it after multiple attempts - e.g. the server is no longer functional, etc.

Other strategies and questions we could/should consider:

  • Should the server be able to tell the UA to pause delivery (i.e. retry-after) for certain amount of time? For example, the collector is being swamped by reports due to site downtime and it doesn't want the client's to unregister entirely, but wants them to back-off and resume later.
  • Should there be logic to deal with per-policy vs. collector-wide cases? For example, if collector is not responsive, it may be removed from all NEL policies that use it vs. just a single policy?
  • ... other cases?

Metadata

Metadata

Assignees

No one assigned

    Labels

    v2Will be considered for a later revision of this spec

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions