Skip to content

[v3.0.1] Prefer https links where available #1422

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

Merged
merged 1 commit into from
Dec 4, 2017

Conversation

MikeRalphson
Copy link
Member

This updates links to apache.org (including in examples), iana.org, ietf.org and semver.org to https for security and consistency. It leaves http links to json-schema.org, yaml.org and commonmark.org as they either don't provide https or Firefox 57 complains about their https setup.

(ping @handrews)

@handrews
Copy link
Member

handrews commented Dec 1, 2017

Sigh. GitHub pages won't allow HTTPS with custom domains (you can do one or the other but not both). And we don't actually own the DNS account, although one of the former JSON Schema editors has a way to pay for it (how that works I do not know). We really need to find some way to claim that account or give up and get a new domain name and host it somewhere that will support HTTPS :-/

@MikeRalphson
Copy link
Member Author

Sigh.

:( as long as you're aware.

@handrews
Copy link
Member

handrews commented Dec 1, 2017

Oh, we are so very aware. It's the same reason why there's a json-schema/json-schema GitHub account still lying around. Someone files a bug on all this at least once or twice a year.

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

Successfully merging this pull request may close these issues.

3 participants