GitHub is now making HTTPS mandatory for all GitHub Pages websites, starting with June 15, 2016, the companyyesterday.
GitHub is the place where most coders go to host their source code. There are alternatives, but GitHub is great and has lots of features.
For open-source aficionados, besides hosting their code, GitHub also lets them build presentation websites, which are internally called GitHub Pages.
These are static HTML websites created with the Ruby-based Jakyll static site generator. The technology is simple and wasby multiple other projects as well.
Until now, GitHub Pages were delivered via HTTP by default, but GitHub users had the option to force HTTPS if authors wanted, with a warning from GitHub’s crew.
“We refrained from officially supporting it [HTTPS for GitHub Pages] because the traffic from our CDN to our servers wasn’t encrypted until now,” GitHub’s Ben Toews explained today.
HTTPS support on the main GitHub service was added many years before. With today’s announcement, GitHub will be moving GitHub Pages over HTTPS, and now almost all of the service’s main features are available over encrypted communications.
Taking into account thatare quite interested in what their citizens are programming or hosting on GitHub, the move needs to be applauded.
Starting June 15, all new username.github.io domains will use HTTPS, and all old ones will be redirected to the HTTPS version automatically. GitHub Pages that use custom domains will remain on HTTP.
.Pages now officially support HTTPS. And it gets an A rating on the Qualys test. Very nice. — brian m. carlson (@bk2204)
No more location.href hacks on GitHub pages to redirect to HTTPS! Yessss— Domenic Denicola (@domenic)
Wake me up whensupports SSL for custom domains — Josh Lockhart (@codeguy)
Not using SSL is becoming harder and harder to justify. Props tofor being on a huge roll, featurewise. — Emil Ong (@OngEmil)
Really excited to help more than a million sites potentially move to HTTPS today and make the net a safer place.— Ben Balter (@benbalter)