Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update proxy setting section #1088

Merged
merged 1 commit into from
May 10, 2017
Merged

Update proxy setting section #1088

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -421,22 +421,22 @@ is invoked for a custom toolchain and it is not available, `rustup`
will attempt to use `cargo` from one of the release channels*,
preferring 'nightly', then 'beta' or 'stable'.

## Working with HTTP proxies
## Working with network proxies

Enterprise networks often don't have direct outside HTTP access, but enforce
the use of HTTP proxies. If you're on such a network, you can request that
the use of proxies. If you're on such a network, you can request that
rustup uses a proxy by setting its URL in the environment. In most cases,
setting `http_proxy` should be sufficient. On a Unix-like system with a
setting `https_proxy` should be sufficient. On a Unix-like system with a
shell like __bash__ or __zsh__, you could use:

```
export http_proxy=http://proxy.example.com:8080
export https_proxy=socks5://proxy.example.com:1080 # or http://proxy.example.com:8080
```

On Windows, the command would be:

```
set http_proxy=http://proxy.example.com:8080
set https_proxy=socks5://proxy.example.com:1080
```

If you need a more complex setup, rustup supports the convention used by
Expand Down