I’m the author of the page. It’s now reachable via HTTPS (again).

I think this is what happened:

I experimented with HTTPS on Sunday and actually got it up and running by patching msafd.dll (see https://jira.reactos.org/browse/CORE-14486 and https://github.com/reactos/reactos/pull/4086).

While the page was running on HTTPS, @timeoperator must have posted this (without me realizing it). Shortly after, the site was down due to the HN Hug of Death®. However, at the time, I thought it had something to do with my recent HTTPS change, so I rolled it back. As a result, the HTTPS link posted here stopped working.

In addition, I wanted to be smart and added a Strict-Transport-Security header:

  add_header Strict-Transport-Security 'max-age=31536000; includeSubDomains; preload' always;

So people who had accessed the HTTPS version (while it was active for a few hours) would never see the non-HTTPS version again.

I didn’t expect it to get so much attention, so next time I attempt something like this, I’ll perform proper load tests, have a dev deployment in place, and check access logs more often!