Having no end of trouble with rustup and cargo behind a web proxy. They both used to work, but now rustup only works with RUSTUP_USE_CURL=1, and cargo doesn't work at all. Proxy is set in the env and in ~/.cargo/config. Anyone seen this? #rustlang
2
4
1
4
does it still not work with rustup 1.18? We had a lot of work done on reqwest for that release. (thanks @jogbert for the cc)
1
It doesn't yet - I managed to get it to self-update by forcing it to use curl, but taking that variable out made it fail. I've just noticed I've got 1.18.1 now, I'll try it again when I'm back in the office tomorrow. Happy to help debug if I can
1
Replying to @mgdm @jogbert
Please do, and file an issue, we've managed to resolve all the proxy-related issues recently with 1.18.0 so hopefully it won't be too hard for us to fix stuff for you too.

Apr 25, 2019 ยท 7:08 PM UTC

1
Replying to @dsilverstone @mgdm @jogbert
Also, if you want to join us on the developer discord to discuss things, I'd be quite happy to do so tomorrow.
1
Cool, I'll try and give it a go tomorrow. Cargo seemed to get stuck when updating the registry, I wondered if it was something to do with libgit2 specifically
1
more replies