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

Customize Content Security Policy (CSP) #41

Open
hakalb opened this issue Feb 14, 2021 · 3 comments
Open

Customize Content Security Policy (CSP) #41

hakalb opened this issue Feb 14, 2021 · 3 comments
Labels
enhancement Make something better priority: major version This issue doesn't have to be handled now but atleast in the next major version

Comments

@hakalb
Copy link
Member

hakalb commented Feb 14, 2021

It's currently all or nothing via secure.d/headers.conf which will for sure not work for all hosted sites. E.g. Grafana needs more flexibility.

This repo uses Caddy and has a nice example of more flexible CSP.

https://github.com/jpcaparas/caddy-csp

@hakalb hakalb added enhancement Make something better priority: major version This issue doesn't have to be handled now but atleast in the next major version labels Feb 14, 2021
@github-actions
Copy link

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@github-actions github-actions bot added the Stale label Mar 22, 2021
@hakalb hakalb removed the Stale label Mar 23, 2021
@github-actions
Copy link

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@github-actions github-actions bot added the Stale label Apr 23, 2021
@github-actions
Copy link

This issue was closed because it has been stalled for 5 days with no activity.

@hakalb hakalb removed the Stale label Aug 27, 2021
@hakalb hakalb reopened this Aug 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Make something better priority: major version This issue doesn't have to be handled now but atleast in the next major version
Development

No branches or pull requests

1 participant