Proxy Support

drush_pm just uses update_status module for communicating with drupal.org. please ask there.

Is the issue in fetching the update information (drush refresh), or in downloading the actual update tarballs themselves? If the former then it is an update_status/core issue - if the latter, then we can help.

To sort out the problems with the downloading of tarballs via wget with drush from behind a proxy, you need to add the proxy server settings to your .wgetrc file.

• On Windows, create a new file in your HOME path named "%HOMEDRIVE%%HOMEPATH%\.wgetrc"
• On Linux/Cygwin create a new file in your home path named ~/.wgetrc

and add the following lines, where {PORT} is the port number of your proxy server:

http_proxy=http://username:password@http.proxy.server:{PORT}
ftp_proxy=http://username:password@ftp.proxy.server:{PORT}
use_proxy=on

I think proxy settings could be considered as being outside the scope of Drush, @jacobwg - would that be sufficient for you?

(Does curl or php-curl support such configurations?)

another technique - http://reluctanthacker.rollett.org/node/114

In my case I do not need the username:password this works as my .wgetrc

http_proxy=http://IP_ADDRESS:80
ftp_proxy=http://IP_ADDRESS:80
use_proxy=on

where IP_ADDRESS is the IP number; and the port is 80

I also had to create C:\tmp for Drush and make it writeable

(Windows 7 32 bit behind a corporate firewall)

Windows 10 user here behind a corporate firewall. Besides obtaining a wget.exe(google wget for windows), adding it to my PATH (system environment variables) I also had to to edit the .wgetrc located at C:/Users/YOURNAME/.wgetrc and add the following lines. (if you don't have a .wgetrc visit gnu.org)

http_proxy=http://proxy.example.com
https_proxy=http://proxy.example.com
ftp_proxy=http://proxy.example.com
check_certificate=off
use_proxy=on