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

[Chore] Update readme to include Content security policy #22

Closed
nwittstruck opened this issue Mar 17, 2022 · 0 comments · Fixed by #23
Closed

[Chore] Update readme to include Content security policy #22

nwittstruck opened this issue Mar 17, 2022 · 0 comments · Fixed by #23

Comments

@nwittstruck
Copy link
Contributor

You can use a content security policy to restrict which resources are being loaded. The app is completely self contained, so you can use quite strict policies. For nginx, this would look like this:

add_header Content-Security-Policy "default-src 'self' img-src 'self' data:; style-src 'self' 'unsafe-inline'" always;

There are couple of inline styles that will be removed in the future, so that unsafe-inline can be removed as well.

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 a pull request may close this issue.

1 participant