https://linuxaudio.org/ works too here...
There goes that theory then. I just highlighted "linuxaudio.org" and right clicked "Open in new tab" and it opened as http.
What theory?
To me it seems that linuxaudio.org web server just doesn't redirect to https automatically, as most of the websites do nowadays.
Compare:
linuxmusicians .com
Code:
$ curl -v -L linuxmusicians.com* Host linuxmusicians.com:80 was resolved.* IPv6: 2a00:d0c0:200:0:d081:faff:fe05:bc62* IPv4: 185.26.156.130* Trying [2a00:d0c0:200:0:d081:faff:fe05:bc62]:80...* Immediate connect fail for 2a00:d0c0:200:0:d081:faff:fe05:bc62: La rete non è raggiungibile* Trying 185.26.156.130:80...* Connected to linuxmusicians.com (185.26.156.130) port 80* using HTTP/1.xGET / HTTP/1.1Host: linuxmusicians.comUser-Agent: curl/8.10.1Accept: */** Request completely sent off< HTTP/1.1 301 Moved Permanently< Server: nginx< Date: Thu, 24 Oct 2024 06:59:48 GMT< Content-Type: text/html< Content-Length: 162< Connection: keep-alive< Location: https://linuxmusicians.com/* Ignoring the response-body* setting size while ignoring< * Connection #0 to host linuxmusicians.com left intact* Clear auth, redirects to port from 80 to 443* Issue another request to this URL: 'https://linuxmusicians.com/'* Host linuxmusicians.com:443 was resolved.* IPv6: 2a00:d0c0:200:0:d081:faff:fe05:bc62* IPv4: 185.26.156.130...with linuxaudio.org
Code:
$ curl -v -L linuxaudio.org* Host linuxaudio.org:80 was resolved.* IPv6: (none)* IPv4: 195.201.118.158* Trying 195.201.118.158:80...* Connected to linuxaudio.org (195.201.118.158) port 80* using HTTP/1.xGET / HTTP/1.1Host: linuxaudio.orgUser-Agent: curl/8.10.1Accept: */** Request completely sent off< HTTP/1.1 200 OK< Date: Thu, 24 Oct 2024 07:01:48 GMT< Server: Apache/2.4.62 (Debian)< Last-Modified: Thu, 13 Jun 2024 18:06:04 GMT< ETag: "189b-61ac95a2e5b00"< Accept-Ranges: bytes< Content-Length: 6299< Vary: Accept-Encoding< Content-Type: text/htmlStatistics: Posted by LAM — Thu Oct 24, 2024 7:03 am