It'd just be nice if HTTPS is failing for some reason.

You mean HTTPS, not SSH...?
Anyway, we are not going to do that as most users wouldn't think to type in the "https://" themselves and would be subjected to an insecure connection. Also, CloudFlare is extremely reliable and if their HTTPS isn't working, it is more than likely that the website would be completely inaccessible, since that would likely be part of a much larger problem.

Thank you for your suggestion.

Jacob G.
Executive director and co-head developer

1) Yes, I do. I was half-asleep when I wrote that.

2) I meant specifically putting a :80 at the end (the port used for regular connections)

3) ...but you aren't in charge of CloudFlare.

2. Believe it or not, the server actually can't tell whether or not you typed in the :80. All it knows is whether you are connecting on port 80 (HTTP) or 443 (HTTPS). Also, the HTTPS management is upstream of our server on CloudFlare, and my options are only "require HTTPS" and "don't require HTTPS", and the second one implements the situation I described in my previous post.

3. No, I'm not. I don't see how that is relevant. The way our system works, CloudFlare communicates with our server over a secure connection, and then it sends the content to the user over a different secure connection. The HTTPS that the end-user sees is managed by CloudFlare.

Jacob G.
Executive director and co-head developer

2) Oh, I didn't actually know that.

3) Oh, I thought CloudFlare was your hosting service (I forgot it was G***i)