Closed cygri closed 8 years ago
Some browsers (at least Chrome) show a warning to the user when including http:// content in a https:// page. This affects pages that use prefix.cc via its APIs. Prefix.cc resolves via https://, but the certificate is invalid.
:+1:
I'd recommend using letsencrypt. Free ssl certificates that support automated renewal
Done, the site is now accessible at http://prefix.cc/ and https://prefix.cc/
Some browsers (at least Chrome) show a warning to the user when including http:// content in a https:// page. This affects pages that use prefix.cc via its APIs. Prefix.cc resolves via https://, but the certificate is invalid.