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-requests] doc reference to wrong document #525

Open

elinesterov opened this issue Jan 9, 2017 · 1 comment

elinesterov commented Jan 9, 2017

Document https://www.w3.org/TR/upgrade-insecure-requests/ uses therminology like "a priori insecure origins" or "potentially secure" with links to mixed content spec (e.g. https://w3c.github.io/webappsec/specs/mixedcontent/#a-priori-insecure-url), but mixed content spec has been updated with a new one, so now when user click on link, he/she navigates to a newer Upgrade Insecure Requests spec, which uses different terminology (e.g. a priori authenticated).

So links in Upgrade Insecure Requests spec https://www.w3.org/TR/upgrade-insecure-requests/, which is https://www.w3.org/TR/2015/CR-upgrade-insecure-requests-20151008/ needs to be updated with links to older Upgrade Insecure Requests spec which is
https://www.w3.org/TR/2015/CR-mixed-content-20151008/

Malvoz commented Oct 8, 2019

Seeing as the new spec location is https://w3c.github.io/webappsec-upgrade-insecure-requests/, and I found that the links to Mixed Content is pointing to the latest version, this issue should be closed.

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