-
Notifications
You must be signed in to change notification settings - Fork 150
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
CSP: Allow directive references. #219
Comments
@mikewest as part of writing a post the CSP pinning feature I had the idea:
Would it make more sense instead of making CSP more complex just allowing the CSP to just contain the integrity of an external CSP file / manifest? |
@jonathanKingston: We've certainly talked about that a lot on the list; the general consensus has been that doing a synchronous request before loading a webpage was too high a price to pay for the feature, but it's potentially reasonable to look back at that discussion again to see if we made the right decision, given how CSP is being used in the wild. |
@mikewest I will raise this again on the mailing list, as you say due to usage it might be worth looking into again (I'll not be upset if it gets shot down). |
Does HTTP/2 header compression not take care of this? Not sure the added complexity is worth it. |
A CSP2 implementation will reject/ignore "script-src 'img-src'" and "style-src 'img-src'" so this is not a backward-compatible change. Like Anne mentioned, it seems like HTTP/2 header compression may solve this problem well enough. |
Rather than repeating hosts all over the place, we could shrink headers (in a backwards incompatible fashion :( ) by allowing one directive to reference another. That is, instead of:
we could conceivably write:
or something similar.
The text was updated successfully, but these errors were encountered: