On 2021/04/11 17:19, Bernhard M. Wiedemann wrote:
On 11/04/2021 17.04, L A Walsh wrote:
I'm not sure how to specify a valid non-ssl mirror automatically or to choose one manually. Seeing how my connection seems to go from normal to SSL during the 1 GET, I'm not sure how to tell if I'm going to get a non-SSL site or not.
You can try this new experimental download redirector:
I used to use one in provo, but found it often didn't have some debug or source packages. But FWIW, the auto-redirect sometimes hits provo: failure: GET http://download.opensuse.org/tumbleweed/repo/src-non-oss/src/frogatto-1.3.1-...: 500 Can't connect to provo-mirror.opensuse.org:443 (SSL connect attempt failed with unknown error error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure)
as it runs in Provo, it could give better performance for US users.
---- I prefer the mirrors over 'here' provo is good when it works, and so are the kernel mirrors, but I was getting double redirects on the kernel mirror system: +0.24 167ms; 2468 (10K/14K) MISS/302 <Ishtar [GET http://download.opensuse.org/tumbleweed/repo/oss/repodata/116419acba72d38a9b... - 195.135.221.134 text/html] +0.25 138ms; 335 (1.4K/2.4K) MISS/301 <Ishtar [GET http://sfo-korg-mirror.kernel.org/opensuse/tumbleweed/repo/oss/repodata/1164... - 149.20.37.36 -] +0.07 65ms; 46 (667/708) TUNNEL/200 <Ishtar [CONNECT mirrors.edge.kernel.org:443 - 147.75.69.165 -] The sfo-korg mirror would seem to usually bump the connection to https on mirrors.edge. mirrors.edge supports http, but I don't get a chance to examine the URL and rewrite https->http before it is resent. I'll try the new mirrors and see what happens... thanks!