Thanks Michael, all seems well with the world again.
Cheers,
David
On 3 February 2016 at 12:49, Michael Snoyman
Sorry about that, I brought it up in issue #150[1] and had thought that cabal-install was no longer a limiting factor on forcing SSL connections. I've just added a workaround that disables the redirect for tarballs, so that it should still work with cabal-install, while granting most users the security guarantees of using SSL. I believe this will be a sufficient workaround, but I'd appreciate if you could test and confirm that this fixes the problem for you.
[1] https://github.com/fpco/stackage-server/issues/150
On Wed, Feb 3, 2016 at 2:13 PM, David Turner < dct25-561bs@mythic-beasts.com> wrote:
Hi,
Overnight there seems to have been a change to stackage where it's now issuing redirects from http to https URLs:
~$ cabal update Downloading the latest package list from stackage-lts-2.22 Warning: http error: Unable to handle redirect, unsupported scheme: https://www.stackage.org/snapshot/lts-2.22/00-index.tar.gz cabal: Failed to download http://www.stackage.org/snapshot/lts-2.22/00-index.tar.gz : ErrorMisc "Error HTTP code: 301"
My cabal doesn't seem to like https and I think it's a recentish version:
$ cabal --version cabal-install version 1.22.0.0 using version 1.22.0.0 of the Cabal library
I'm probably using a bit of an old workflow (and I know that LTS-2 is pretty old too) but is there any simple way of getting this working again?
Cheers,