Due to recent changes in 0.11.5 and 1.0 where various ciphers were removed off the default list, it got me thinking about errors.
In this instance an older client that connects will not get any error, just a failure to connect. It will if the client is good say that it was unable to establish a secure connection. It simply looks like the website doesnt exist.
Since in all likelyhood the initial connection was
HTTP which was then redirected to
HTTPS , if caddy is unable to create a secure connection after having been redirected from
HTTP should it show an error over
This at least would enable us to let the user know that the website does exist but the client has been unable to establish a secure connection.