adopted-ember-addons/ember-cli-content-security-policy

Use report-to instead of the deprecated report-uri

Open

#166 opened on Nov 24, 2020

View on GitHub
 (1 comment) (0 reactions) (0 assignees)JavaScript (46 forks)github user discovery
enhancementgood first issue

Repository metrics

Stars
 (157 stars)
PR merge metrics
 (PR metrics pending)

Description

The new Reporting API is not supported by all browsers yet, so this isn't something we need to move on for at least another year or so. As of November 2020 it's not yet supported by Firefox or Safari.

https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/report-to

  1. At some point we'll want to add support for report-to in addition to report-uri. With both are present and the browser support both, report-to takes precedence.
  2. Separately, when all browsers supported by ember has support for report-to we'll want to drop the report-uri value.

Opened since @jelhan asked me to: https://github.com/rwjblue/ember-cli-content-security-policy/issues/148

Background

Contributor guide

Research direction
Investigate the current CSP implementation in the addon, add support for the `report to` directive while retaining `report uri` for backward compatibility, and ensure proper browser detection or conditional inclusion.
Tech stack
javascript
Domain
securitybackend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Ember CLIContent Security Policy
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40