Allow to pass nonce option to getBrowserTimingHeader. #266
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.
CHANGE LOG
nonce
to getBrowserTimingHeader()INTERNAL LINKS
https://discuss.newrelic.com/t/content-security-policy-and-browser-injection/2629/42
NOTES
getBrowserTimingHeader
generates an inline script tag. This is generally a bad practice if you want to protect your page with HTTP Content-Security-Policy (CSP) header. In the situations you do require it you should generate and pass anonce
UUID which tells the browser those scripts are allowed to be executed.This PR adds an option to add a
nonce
attribute to the generated<script>
tag.Currently we're injecting the nonce in the middle of the returned string header with
String.substr()
- which is not ideal.