Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create Content-Security-Policy headers #141

Closed
phax opened this issue Jul 22, 2020 · 1 comment
Closed

Create Content-Security-Policy headers #141

phax opened this issue Jul 22, 2020 · 1 comment

Comments

@phax
Copy link
Owner

phax commented Jul 22, 2020

For the default SMP.
Add a configuration option to disable the CSP setting to restore the old behaviour.
Add a status item to indicate, if CSP header is emitted or not.

@phax phax self-assigned this Jul 22, 2020
phax added a commit that referenced this issue Aug 14, 2020
@phax
Copy link
Owner Author

phax commented Aug 14, 2020

Part of 5.2.6 release. New webapp.properties are:

  • csp.enabled (since 5.2.6): enable or disable the output of the "Content Security Policy" HTTP headers. By default this is enabled.
  • csp.reporting.only (since 5.2.6): enable or disable the reporting of CSP issues only. So no content will be blocked if CSP is enabled but a CSP violation is found. By default this is disabled. The reporting URI inside the SMP is always /smp-cspreporting.
  • csp.reporting.enabled (since 5.2.6): enable or disable the reporting of CSP issues if something is blocked. This only has an effect, if csp.enabled is true and csp.reporting.only is false. By default this is disabled. The reporting URI inside the SMP is always /smp-cspreporting.

@phax phax closed this as completed Aug 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant