proxy settings for the command line
ShareWhen using applications from the command line,
you will sometimes need to setup a specific proxy for them to use, if you don’t have a direct access to the Internet from the server you are working on.
in some of these application you can setup this through the app switches itself, but simpler apps just use the system network settings.
to fix this you can first check what current settings you have now with:
ENV | grep -i proxy
this should show you the current proxy settings you have.
to add your own settings do:
export http_proxy=”http://<proxy-server-ip>:<port>”
export ftp_proxy=”http://<proxy-server-ip>:<port>”
for example:
export http_proxy=”http://192.168.0.10:8080″
after that, just run your command line app, it should pick up and use these settings.
Related posts:
- check smtp from commnad line
- Test http server from windows command line
- Check apache from command line
- Linux Commands – Top 20 Most Used
- Linux Server Information – The Easy Way
5 Responses to “proxy settings for the command line”
Leave a Reply
thorn on May 7th, 2009
Although its quite old and I haven’t tested it recently, there is tsocks (http://tsocks.sourceforge.net/about.php) and probably some other solutions out there who can transparently connect your application using a socks proxy even if the application doesn’t support it.
Paid Proxy on May 11th, 2009
Crazy how many people still use and others profit with web proxies.
proxy bypass on January 17th, 2010
you can use my proxy site for surfing the web anonymously
onetom on April 1st, 2010
we use an “ssh -D 1080 company.server socks5″ proxy as a simple VPN-like solution to access the intranet (which is in a datacenter) from our workstations.
proxies are not just about anonymity…
they are like a glue between services.
you can plug in services to a proxy and provide common features to them, like authentication, authorization, load balancing, clustering, caching, logging.
this allows you to keep the services simple and hence robust and abstracted from the actual infrastructure they are built into.
yonitg on April 5th, 2010
onetom: sure, the whole post wasnt just about anonymity – it was aimed at allowing Linux command line applications reach the internet via an internal proxy server. I totally agree