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

Upgrade Insecure Content #63

Open
Mikaela opened this issue Sep 23, 2015 · 0 comments
Open

Upgrade Insecure Content #63

Mikaela opened this issue Sep 23, 2015 · 0 comments

Comments

@Mikaela
Copy link
Contributor

Mikaela commented Sep 23, 2015

Sorry if this is already supported

The upgrade insecure content header or meta description tells the browser that it should use SSL, possibly related to #53 and #61.

http://caniuse.com/#feat=upgradeinsecurerequests has links to resources on it and I think reading headers would have the same issue as with HSTS, but maybe it could be partially supported with the meta tag?
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
1 participant
@Mikaela