Un-deprecated 'child-src'
'child-src' is now part of the fallback chain for 'worker-src'. This means that 'child-src' always takes precedence over 'script-src' when checking worker requests. Added extra tests to ensure that a worker request blocked by 'child-src' and allowed by 'script-src' is blocked. Removed previous logic that considered 'script-src' to be the fallback for 'worker-src' and amended tests. Removed "temporary" logic put in place to not break sites using "child-src". Refactored the OperativeDirective logic to ensure that the caller does not need to be aware of precise fallback chain of the directive, otherwise the way to get the 'worker-src' operative directive would be: OperativeDirective(worker_src_.Get(), OperativeDirective(child_src_.Get(), OperativeDirective(script_src_.Get()))); To be submitted with the spec PR as it includes tests. Spec: https://github.com/w3c/webappsec-csp/pull/313 Bug: 669496 Change-Id: I7ca9552df1d0ce203a604b0e469a268f6b112e49 Reviewed-on: https://chromium-review.googlesource.com/1128087 Commit-Queue: Andy Paicu <andypaicu@chromium.org> Reviewed-by:Mike West <mkwst@chromium.org> Cr-Commit-Position: refs/heads/master@{#573278}
Showing
This diff is collapsed.
Please register or sign in to comment