Fix CSP Report #274
Merged
Fix CSP Report #274
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Not firing on all cylinders today. How does one go about triggering a csp-report? Postman is not cooperating. |
I just triggered it by changing the CSP to have a failure, like commenting out the line which allows us to use google-analytics for example. I'm not sure of a good way to do it artificially though I would think postman should work as long as you get the weird content-type correct. |
|
closes #273 |
sprucely
approved these changes
Sep 9, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
CSP Report has always been broken -- the JSON format wasn't handled by the parser but more importantly the content-type for CSP reports isn't application/json so that requires modifying the default input formatter.