Use HTTPS about buckler HOT 7 OPEN

Also #27 was a kind've nasty issue.

@jbowes Might be worth looking into https://www.globalsign.com/ssl/ssl-open-source/ for Buckler, even if people are expected to eventually transition to Shields.io.

from buckler.

+1

What about startssl?

from buckler.

Well, maybe it doesn't make much difference any more. badges/shields#111

from buckler.

Not really. GitHub isn't the only place README.md content appears. NPM shows it and (I think) PyPI often shows it, too.

from buckler.

Both shields.io and b.repl.ca are available under https, but in both cases the certificate does not match the hostname.

An alternative found by @ralphbean is to use https://buckler-bowes.rhcloud.com/v1/.... instead of http://b.repl.ca/v1/.... which then provides the shield behind https and provides a certificate matching the hostname.

from buckler.

Both shields.io and b.repl.ca are available under https, but in both cases the certificate does not match the hostname.

Ah, that is true of the base https://shields.io domain, but https://img.shields.io actually has a valid cert (and that's the sub domain you need for requesting images). Check output of openssl s_client -showcerts -connect img.shields.io:443 to see.

from buckler.

Ah ok @ralphbean looks like I went too fast, thanks for the info! :)

from buckler.