# Your browser might be too new for the no-ssl version of this site

Some browsers will try to upgrade to HTTPS if a domain has an SRV or HTTPS
record in the DNS response. This site uses the free tier of Cloudflare, which
automatically adds the HTTPS record if HTTP2 is enabled. Disabling HTTP2 for
a single subdomain is not possible unless I pay for an enterprise plan, which
I don't plan to do any time soon. Nor do I plan to fully disable HTTP2 (that
is, for all subdomains of the site).

As far as I can tell, Edge/Chrome are more aggressive with this, and can fall
into a redirect loop, but Firefox is fine, and I can't test Safari.

The target audience/browsers for no-ssl are old versions of Internet Explorer,
and wouldn't check for SRV or HTTPS, as they predate these new DNS records.

To avoid a redirect loop on Edge/Chrome, an HTTPS-to-HTTP redirect wasn't used.

Try to manually access this page with `HTTP://`, and if you do not get
redirected automatically to this `HTTPS://` version, your browser can use the
no-ssl version. That said, if you can read this, you shouldn't be using
this no-ssl version, unless you plan to open this no-ssl version in a different
browser which can't read this.

Old versions of Internet Explorer need this subdomain because they only support
HTTPS using SSL, which is insecure when compared to HTTPS using TLS, so a site
that redirects to HTTPS will prevent users of IE6/IE7/etc from accessing it.

At the same time, it would be misleading to use SSL as this would show up as
secure in the browser UI (locked padlock), but isn't actually secure anymore.