Closed practik closed 4 years ago
HTTPZ does not redirect that one back to HTTP because the server is effectively responding with an encrypted response. If you take a peek at the site's security info, you'll see it is using a certificate issued by USERTrust RSA.
Nevertheless, the server returns a 503 status code (Service Unavailable). The problem is that status code is too generic (not necessarily related to HTTPS in general). If HTTPZ treated those as errors, it would be taking wild guesses, and would sometimes downgrade requests mistakenly.
Bottom line, this is the sort of scenario that users are meant to solve via whitelisting.
Thanks anyway for reporting.
this is the sort of scenario that users are meant to solve via whitelisting.
Done, and thanks for the explanation!
^ What the title says. ^ Instead of redirecting back to
http://archives.nypl.org
, you get stuck onhttps://archives.nypl.org
, which shows you this error message:archives.nypl.org - SSL Connection failed Error code 29 SSL is not supported