UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.86 Safari/537.36
Steps to reproduce the problem:
1. Display a web page that use CSP without "unsafe-inline" directive
2. Gather the directive violation report using the CSP report-uri directive
3. Chromium does not provide "script-sample" property in the violation report payload
What is the expected behavior?
Firefox provides as "script-sample" property that ease a lot the false positive detection.
What went wrong?
Nothing went wrong, it's a feature request. At the moment, it's difficult to detect whether there's an issue in the generated content or if it's a third party extension that triggered the CSP violation.
Did this work before? No
Chrome version: 50.0.2661.86 Channel: stable
OS Version: OS X 10.11.4
Flash Version: Shockwave Flash 21.0 r0
As a resource, here's the piece of code of gecko that adds this property https://github.com/mozilla/gecko-dev/blob/3c5ee70a185407483b2040a3d32fa6da7f91560f/dom/security/nsCSPContext.cpp#L840-L844
Comment 1 by rsesek@chromium.org
, Apr 26 2016Components: Blink>SecurityFeature
Labels: -Type-Bug-Security -Restrict-View-SecurityTeam -OS-Mac OS-All Type-Feature
Status: Untriaged (was: Unconfirmed)