This repository has been archived by the owner on Jan 14, 2022. It is now read-only.
Content security policy issue - Closes #808 #811
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What was the problem?
After implementation of
Google Tag Manager
the console intermittently shows aimg-src
CSP violation. It happens because GTM loads some assets onto the page to keep track of it and for some reason the source of these assets can change based on the location where the page is accessed.How did I fix it?
As the list of possibles domains for google is very long (google.com, google.de, google.co.uk, etc..) to be whitelisted, I've expanded the
img-src
policy to any secure source (https).In addition, I've restricted the
script-src
by removing theunsafe-inline
and adding the inline script hash instead.How to test it?
Load the page and check the console.
Review checklist
commit guidelines