HTTPArchive/legacy.httparchive.org

Set up an SSL cert for httparchive.org

rviscomi opened this issue · 9 comments

rviscomi commented

I hear that HTTPS thing is getting popular.

pmeenan commented

I've set up lets-encrypt on WPT and it should be easy enough to do on HA with the nginx support. Only complication is the nginx server reverse-proxies the HA requests to an apache server so not sure if the webroot will "just work" or if it will need a few tweaks.

rviscomi commented

I just gave certbot a whirl and it failed to download a bunch of dependencies, which I think is a symptom of our version of Ubuntu being old.

The beta site is hosted on App Engine and the current site will become old.httparchive.org or something, so maybe it makes more sense to wait for the musical subdomains to settle down before setting up certs.

igrigorik commented

Yeah, I'd focus on HTTPS for the new (GAE-powered) site, with a view that we want to sunset current site asap -- lack of HTTPS being one of many reasons.

rviscomi commented

TODO:

  • migrate the beta site from its own GAE project to the primary httparchive project
  • set up a wildcard cert for GAE-hosted sites, to support the beta site in both dev (beta.httparchive.org) and prod (httparchive.org) stages
rviscomi commented

TODO(self): Need to confirm that the cert for the beta subdomain will work when it becomes the primary domain. If so this issue is ok to close.

pmeenan commented

The legacy server is https now (httparchive.org, www, dev, desktop, mobile, chrome)

  • 👍1
rviscomi commented

Pat, I set up a new A record for legacy.httparchive.org. Is the https cert a wildcard?

pmeenan commented

No. Should be able to be added with certbot (I'll do it on Monday)

pmeenan commented

Cert has been expanded

  • 👍1