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.

Sign up for GitHub

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

Jump to bottom

Take Content-Security-Policy: upgrade-insecure-requests into account. #25

Open
bramus opened this issue Jun 9, 2015 · 2 comments
Open

Take Content-Security-Policy: upgrade-insecure-requests into account. #25

bramus opened this issue Jun 9, 2015 · 2 comments

Comments

@bramus
Copy link
Owner

bramus commented Jun 9, 2015

The new upgrade-insecure-requests Content Security Policy directive can be used to transparently upgrade insecure resource requests to secure variants. This avoids the mixed content warnings without having to modify the HTML documents at all.

Source: https://dev.opera.com/blog/opera-30/
More details: http://www.w3.org/TR/upgrade-insecure-requests/
@mathiasbynens
Copy link
Collaborator

The living spec is here: https://w3c.github.io/webappsec/specs/upgrade/ (Don’t link to TR copies)

bramus added a commit that referenced this issue Jun 3, 2016
@bramus
Add a todo regarding Content-Security-Policy (see #25)
cd705de
@michaelblyons
Copy link

If you add this, please include an option to disable it for the purposes of scanning.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mathiasbynens @bramus @michaelblyons