CSP: 'violated-directive' should match 'effective-directive'.
In [1], mikispag@ noted that we're currently returning the entire
text of the violated directive, including its source list, etc. This
information is replicated in the report via the 'original-policy'
property, and CSP3 defines both 'violated-directive' and
'effective-directive' to contain the same data.
This patch changes our implementation in line with the spec.
[1]: https://github.com/w3c/web-platform-tests/pull/4020R=jochen@chromium.org
Committed: https://crrev.com/0e64be9cf335ee3bea7c989702c5a9a0934af037
Cr-Commit-Position: refs/heads/master@{#427634}
Description was changed from
==========
CSP: 'violated-directive' should match 'effective-directive'.
We're currently returning the entire text of the violated directive,
including its source list, etc. This information is replicated in the
report via the 'original-policy' property, and CSP3 defines both
'violated-directive' and 'effective-directive' to contain the same
data.
This patch changes our implementation in line with the spec.
R=jochen@chromium.org
==========
to
==========
CSP: 'violated-directive' should match 'effective-directive'.
In [1], mikispag@ noted that we're currently returning the entire
text of the violated directive, including its source list, etc. This
information is replicated in the report via the 'original-policy'
property, and CSP3 defines both 'violated-directive' and
'effective-directive' to contain the same data.
This patch changes our implementation in line with the spec.
[1]: https://github.com/w3c/web-platform-tests/pull/4020R=jochen@chromium.org
==========
commit-bot: I haz the power
The CQ bit was unchecked by commit-bot@chromium.org
4 years, 1 month ago
(2016-10-26 08:23:33 UTC)
#10
Message was sent while issue was closed.
Committed patchset #1 (id:1)
commit-bot: I haz the power
Description was changed from ========== CSP: 'violated-directive' should match 'effective-directive'. In [1], mikispag@ noted that ...
4 years, 1 month ago
(2016-10-26 08:25:30 UTC)
#11
Message was sent while issue was closed.
Description was changed from
==========
CSP: 'violated-directive' should match 'effective-directive'.
In [1], mikispag@ noted that we're currently returning the entire
text of the violated directive, including its source list, etc. This
information is replicated in the report via the 'original-policy'
property, and CSP3 defines both 'violated-directive' and
'effective-directive' to contain the same data.
This patch changes our implementation in line with the spec.
[1]: https://github.com/w3c/web-platform-tests/pull/4020R=jochen@chromium.org
==========
to
==========
CSP: 'violated-directive' should match 'effective-directive'.
In [1], mikispag@ noted that we're currently returning the entire
text of the violated directive, including its source list, etc. This
information is replicated in the report via the 'original-policy'
property, and CSP3 defines both 'violated-directive' and
'effective-directive' to contain the same data.
This patch changes our implementation in line with the spec.
[1]: https://github.com/w3c/web-platform-tests/pull/4020R=jochen@chromium.org
Committed: https://crrev.com/0e64be9cf335ee3bea7c989702c5a9a0934af037
Cr-Commit-Position: refs/heads/master@{#427634}
==========
commit-bot: I haz the power
Patchset 1 (id:??) landed as https://crrev.com/0e64be9cf335ee3bea7c989702c5a9a0934af037 Cr-Commit-Position: refs/heads/master@{#427634}
4 years, 1 month ago
(2016-10-26 08:25:32 UTC)
#12
Issue 2447003002: CSP: 'violated-directive' should match 'effective-directive'.
(Closed)
Created 4 years, 1 month ago by Mike West
Modified 4 years, 1 month ago
Reviewers: jochen (gone - plz use gerrit)
Base URL:
Comments: 0