<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">I thought activating that option required HTTPS and a valid SSL cert on the source site too. At least that’s what it seemed to be recently when I tried that (with my own website, also currently hosted off of Github Pages).<div class=""><br class=""></div><div class=""> -hilmar</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Sep 14, 2017, at 8:10 PM, Shyam Saladi <<a href="mailto:saladi1@illinois.edu" class="">saladi1@illinois.edu</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="">A minor point, but I think that Cloudflare can redirect http to https:</div><div class=""><br class=""></div><div class=""><a href="https://support.cloudflare.com/hc/en-us/articles/200170536-How-do-I-redirect-all-visitors-to-HTTPS-SSL-" class="">https://support.cloudflare.com/hc/en-us/articles/200170536-How-do-I-redirect-all-visitors-to-HTTPS-SSL-</a><br class=""></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Thu, Sep 14, 2017 at 3:18 PM, Hilmar Lapp <span dir="ltr" class=""><<a href="mailto:hlapp@drycafe.net" target="_blank" class="">hlapp@drycafe.net</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Not directly, that's correct. However, there are at least three alternatives, each with various pros and cons.<br class="">
<br class="">
1) We could front the site with Cloudflare. This would give us a free SSL cert from Cloudflare. It would not redirect http to https, and would require moving DNS for the domain to Cloudflare.<br class=""></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br class="">
2) Proxy the traffic from <a href="http://github.io" class="">Github.io</a> through our Apache server on AWS. This would allow us to redirect http to https, and we'd use a Let's Encrypt SSL cert. For Apache the LE certbot can auto-renew, I think. In essence this is us doing some of what Cloudflare would do, except for DDOS protection, so the site would then have a single point of failure.<br class="">
<br class="">
3) Use Gitlab Pages for hosting. This would allow SSL certs for custom domains. My understanding is they also support Let's Encrypt for cert renewal, but I haven't tried that yet. Downside is that now we're hosting the repo in a different place than everything else Bioperl. I also don't know about redirecting http to https.<br class="">
<br class="">
-hilmar<br class="">
<br class="">
Sent from away<br class="">
<div class="gmail-HOEnZb"><div class="gmail-h5"><br class="">
> On Sep 14, 2017, at 5:42 PM, Peter Cock <<a href="mailto:p.j.a.cock@googlemail.com" class="">p.j.a.cock@googlemail.com</a>> wrote:<br class="">
><br class="">
> As far as I know, using your own domain with<br class="">
> GitHub pages and HTTPS is still not possible.<br class="">
><br class="">
> Peter<br class="">
><br class="">
>> On Thu, Sep 14, 2017 at 6:10 PM, Carnë Draug <<a href="mailto:carandraug%2Bdev@gmail.com" class="">carandraug+dev@gmail.com</a>> wrote:<br class="">
>> Hi<br class="">
>><br class="">
>> If you access <a href="https://bioperl.org/" rel="noreferrer" target="_blank" class="">https://bioperl.org</a> you will get a SSL_ERROR_BAD_CERT_DOMAIN<br class="">
>><br class="">
>> The problem is that current certificate is only valid for <a href="http://github.io/" rel="noreferrer" target="_blank" class="">github.io</a><br class="">
>> domains.<br class="">
>><br class="">
>> Carnë<br class="">
>><br class="">
>> ______________________________<wbr class="">_________________<br class="">
>> Bioperl-l mailing list<br class="">
>> <a href="mailto:Bioperl-l@mailman.open-bio.org" class="">Bioperl-l@mailman.open-bio.org</a><br class="">
>> <a href="http://mailman.open-bio.org/mailman/listinfo/bioperl-l" rel="noreferrer" target="_blank" class="">http://mailman.open-bio.org/<wbr class="">mailman/listinfo/bioperl-l</a><br class="">
><br class="">
> ______________________________<wbr class="">_________________<br class="">
> Bioperl-l mailing list<br class="">
> <a href="mailto:Bioperl-l@mailman.open-bio.org" class="">Bioperl-l@mailman.open-bio.org</a><br class="">
> <a href="http://mailman.open-bio.org/mailman/listinfo/bioperl-l" rel="noreferrer" target="_blank" class="">http://mailman.open-bio.org/<wbr class="">mailman/listinfo/bioperl-l</a><br class="">
<br class="">
______________________________<wbr class="">_________________<br class="">
Bioperl-l mailing list<br class="">
<a href="mailto:Bioperl-l@mailman.open-bio.org" class="">Bioperl-l@mailman.open-bio.org</a><br class="">
<a href="http://mailman.open-bio.org/mailman/listinfo/bioperl-l" rel="noreferrer" target="_blank" class="">http://mailman.open-bio.org/<wbr class="">mailman/listinfo/bioperl-l</a></div></div></blockquote></div><br class=""></div></div>
</div></blockquote></div><br class=""><div class="">
<div class=""><div style="font-family: Monaco; font-size: 11px; orphans: 2; widows: 2;" class="">-- </div><div style="font-family: Monaco; font-size: 11px; orphans: 2; widows: 2;" class="">Hilmar Lapp -:- <a href="http://lappland.io" class="">lappland.io</a></div></div><div class=""><br class=""></div><br class="Apple-interchange-newline">
</div>
<br class=""></div></body></html>