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

recommend setting base-uri to 'none' (ideally), 'self' or at least a specific domain (rarely needed) in Content Security Policy #525

Closed
thestinger opened this issue Mar 23, 2021 · 2 comments · Fixed by #809
Assignees
Milestone

Comments

@thestinger
Copy link

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 to none to get rid of the attack surface.

@baknu
Copy link
Contributor

baknu commented May 4, 2021

See also: #325 (comment)

@baknu baknu added this to the v1.5 milestone May 4, 2021
@baknu baknu modified the milestones: v1.5, v1.6 Nov 12, 2021
@mxsasha mxsasha self-assigned this Oct 20, 2022
@mxsasha mxsasha closed this as completed in f5fcc99 Mar 8, 2023
@baknu baknu self-assigned this Mar 15, 2023
@baknu
Copy link
Contributor

baknu commented Mar 20, 2023

CSP

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging a pull request may close this issue.

3 participants