-
Notifications
You must be signed in to change notification settings - Fork 37
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
recommend setting base-uri to 'none' (ideally), 'self' or at least a specific domain (rarely needed) in Content Security Policy #525
Comments
See also: #325 (comment) |
mxsasha
added a commit
that referenced
this issue
Nov 17, 2022
mxsasha
added a commit
that referenced
this issue
Nov 17, 2022
mxsasha
added a commit
that referenced
this issue
Jan 9, 2023
mxsasha
added a commit
that referenced
this issue
Jan 9, 2023
mxsasha
added a commit
that referenced
this issue
Jan 9, 2023
mxsasha
added a commit
that referenced
this issue
Jan 9, 2023
mxsasha
added a commit
that referenced
this issue
Mar 8, 2023
mxsasha
added a commit
that referenced
this issue
Mar 8, 2023
CSP |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This controls the base URI set by the
<base>
feature. As far as I know, that's rarely used or at least is contained within the same origin. Nearly every site should be able to set this tonone
to get rid of the attack surface.The text was updated successfully, but these errors were encountered: