Actually a more likely scenario is:
The old link used to be
http://calibre.kovidgoyal.net/. Today when you clicked on that link it should have redirected you to
http://calibre-ebook.com. The issue is that calibre.kovidgoyal.net is a subdomain of kovidgoyal.net.
https://kovidgoyal.net exists and uses headers to tell your browser that it must follow only HTTPS connection of its domain and subdomains:
Code:
$ curl -svo /dev/null https://kovidgoyal.net/
* Trying 166.78.104.224...
* Connected to kovidgoyal.net (166.78.104.224) port 443 (#0)
* found 173 certificates in /etc/ssl/certs/ca-certificates.crt
* found 697 certificates in /etc/ssl/certs
* ALPN, offering http/1.1
* SSL connection using TLS1.2 / ECDHE_RSA_AES_128_GCM_SHA256
* server certificate verification OK
* server certificate status verification SKIPPED
* common name: kovidgoyal.net (matched)
* server certificate expiration date OK
* server certificate activation date OK
* certificate public key: RSA
* certificate version: #3
* subject: CN=kovidgoyal.net
* start date: Sun, 08 Jan 2017 06:45:00 GMT
* expire date: Sat, 08 Apr 2017 06:45:00 GMT
* issuer: C=US,O=Let's Encrypt,CN=Let's Encrypt Authority X3
* compression: NULL
* ALPN, server accepted to use http/1.1
> GET / HTTP/1.1
> Host: kovidgoyal.net
> User-Agent: curl/7.47.0
> Accept: */*
>
< HTTP/1.1 200 OK
< Server: nginx
< Date: Tue, 10 Jan 2017 21:12:23 GMT
< Content-Type: text/html; charset=utf-8
< Content-Length: 2456
< Last-Modified: Thu, 25 Aug 2016 23:34:10 GMT
< Connection: keep-alive
< ETag: "57bf8072-998"
< Strict-Transport-Security: max-age=10886400; includeSubdomains
< Accept-Ranges: bytes
<
{ [2456 bytes data]
* Connection #0 to host kovidgoyal.net left intact
See the Strict-Transport-Security: max-age=10886400; includeSubdomains header.
Because there is no HTTPS version of the old link (try:
https://calibre.kovidgoyal.net/) you get the error you're seeing.
Anyways... thanks again, replacing the link fixed the issue.
