HTTP proxy
Jump to navigation
Jump to search
To allow HTTP requests reach the outside world, we maintain a caching HTTP proxy in each datacenter. They are exposed using services entries of the form webproxy.<datacenter>.wmnet. These proxies are not meant to be used from Cloud VPS instances.
As of 20th August 2019, the entries are:
| Service Name | Server | port |
|---|---|---|
| webproxy.eqiad.wmnet | install1003.wikimedia.org | 8080 |
| webproxy.codfw.wmnet | install2003.wikimedia.org | 8080 |
| webproxy.esams.wmnet | install1003.wikimedia.org | 8080 |
| webproxy.ulsfo.wmnet | install2003.wikimedia.org | 8080 |
| webproxy.eqsin.wmnet | install2003.wikimedia.org | 8080 |
You can set the http_proxy and https_proxy environment variables to make many command-line scripts use the site specific proxy automatically. Add these lines to your ~/.profile file.
export http_proxy=http://webproxy:8080
export https_proxy=http://webproxy:8080
export no_proxy=127.0.0.1,localhost,.wmnet
You can also set these variables for your current session only by running the same commands at the terminal prompt.
curl
If you are using curl, you can use the --proxy flag:
curl --proxy http://webproxy.eqiad.wmnet:8080 http://www.google.com
Reference
See also
- url-downloader (another set of squid proxies for slightly different use cases)
- T254011: Why do we have 2 sets of squid proxies?