Support HTTPS #216

Closed
opened 2026-02-17 11:35:36 -06:00 by GiteaMirror · 4 comments
Owner

Originally created by @bhubbard on GitHub (Apr 18, 2016).

http://semver.org should default to HTTPS. This can easily be accomplished with a service like CloudFlare.

Originally created by @bhubbard on GitHub (Apr 18, 2016). http://semver.org should default to HTTPS. This can easily be accomplished with a service like CloudFlare.
Author
Owner

@martinsuchan commented on GitHub (Sep 15, 2016):

...or with a free domain certificate from Let's Encrypt.

@martinsuchan commented on GitHub (Sep 15, 2016): ...or with a free domain certificate from [Let's Encrypt](https://letsencrypt.org/).
Author
Owner

@dragon788 commented on GitHub (Dec 1, 2016):

Definitely should either do CloudFlare or Let's Encrypt to get HTTPS, was really sad when I was going to link somebody to https://semver.org and got a cert warning.

@dragon788 commented on GitHub (Dec 1, 2016): Definitely should either do CloudFlare or Let's Encrypt to get HTTPS, was really sad when I was going to link somebody to https://semver.org and got a cert warning.
Author
Owner

@dragon788 commented on GitHub (Dec 1, 2016):

This should be closed like #186 and any further votes/comments made over at https://github.com/mojombo/semver.org/issues/86 .

@dragon788 commented on GitHub (Dec 1, 2016): This should be closed like #186 and any further votes/comments made over at https://github.com/mojombo/semver.org/issues/86 .
Author
Owner

@haacked commented on GitHub (Dec 1, 2016):

Agreed.

@haacked commented on GitHub (Dec 1, 2016): Agreed.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/semver#216