Skip to content

Conversation

@aravinda3001
Copy link

Content-Security-Policy : Wildcard Directive

Changes proposed in the pull request

  • Ensure that web server, application server, load balancer, etc. is properly configured to set the Content-Security-Policy header.

Impact

The configurations either allow wildcard sources (or ancestors), are not defined, or are overly broadly defined: frame-ancestors, form-action

Other information

Reference:
http://www.w3.org/TR/CSP2/
http://www.w3.org/TR/CSP/
http://caniuse.com/#search=content+security+policy
http://content-security-policy.com/
https://github.com/shapesecurity/salvation
https://developers.google.com/web/fundamentals/security/csp#policy_applies_to_a_wide_variety_of_resources

iammosespaulr and others added 30 commits January 20, 2018 00:18
Update main.html   CORRECTING SPELLING ERRORS
Updated for clarity in subheadings
Official chatroom badge added
Update Dockerfile and correct error
Separate app and server for fast testing execution and getting coverage metrics of the code
Signed-off-by: Bhavya Aggarwal <[email protected]>
Signed-off-by: Bhavya Aggarwal <[email protected]>
Signed-off-by: Bhavya Aggarwal <[email protected]>
Signed-off-by: Bhavya Aggarwal <[email protected]>
Signed-off-by: Bhavya Aggarwal <[email protected]>
Signed-off-by: Bhavya Aggarwal <[email protected]>
shivamarora96 and others added 30 commits August 3, 2018 22:55
…ular2-stacks

# Conflicts:
#	stackle_api/package-lock.json
PostLikes Array Added in Userschema .Comments and Replies Enpoints added
Merge pull request #136 from shivamarora96/master
Stacks Functionality Implementation
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.