It gives this wonderful error message:
40536FA8:error:10000093:BIO routines:BIO_do_connect_retry:connection timeout:../../openssl/crypto/bio/bio_lib.c:969:
the reason is that Avalanche attempts to read https://www.unsatisfactorysoftware.co.uk/ver.php?f=avalanche directly, and it doesn't support proxy for https, it doesn't care about $http_proxy or $https_proxy variables.
A program that is supposed to be a small and efficient tool to open archives should not need to have its own networking and TLS handling code, so perhaps a better idea would be to leave http/https handling to dedicated tools that already do this very well, for example aget in the UHC-Tools package?
(Also I'd do the version string checks against release on aminet (http://aminet.net/util/arc/avalanche.readme) rather than a dedicated URL that would need to be "forever" maintained. Upon discovery of newer version, it seems naturally to offer to download the new version, and ...ehm... open the archive?)
It gives this wonderful error message:
40536FA8:error:10000093:BIO routines:BIO_do_connect_retry:connection timeout:../../openssl/crypto/bio/bio_lib.c:969:
the reason is that Avalanche attempts to read https://www.unsatisfactorysoftware.co.uk/ver.php?f=avalanche directly, and it doesn't support proxy for https, it doesn't care about $http_proxy or $https_proxy variables.
A program that is supposed to be a small and efficient tool to open archives should not need to have its own networking and TLS handling code, so perhaps a better idea would be to leave http/https handling to dedicated tools that already do this very well, for example aget in the UHC-Tools package?
(Also I'd do the version string checks against release on aminet (http://aminet.net/util/arc/avalanche.readme) rather than a dedicated URL that would need to be "forever" maintained. Upon discovery of newer version, it seems naturally to offer to download the new version, and ...ehm... open the archive?)