Windows Proxy to Use tools such as Lynx, Deploy on Corporate Network

From Kb

Jump to: navigation, search

Contact Article Author | Blog of Article Author | FirstPartners.net Home | LinkedIn profile of Author

Contents

See Also

General Problem - Authenication Proxy

  • Most Corporate Networks use an authenicating proxy , tied to Windows NT username , to access internet resources.
  • Firefox and Internet Explorer can use these resouces (almost) automatically by passing NT username and password.
  • Command line tools, such as Lynx and Wget are unable to pass these settings.
  • Depending on the corporate network setup, the proxy can sometimes also interfere with local network traffic (e.g. Deploying to Weblogic using Maven)

Solution

  • Use the above script (NTLM Authorisation Proxy Server) to proxy on our behalf; all traffic remains the same, but the proxy adds the needed authenication (headers) behind the scenes.
  • You will need to configure your local program to use the proxy that you are running

Install and Run Notes

  • Install Python and/or Jython
  • Download script from above source and extract to convenient location
  • Change the config (as per notes in readme.txt)
  • run the script
  • Run our program, but pass in params so that is uses localhost: 5865

IP Address Proxy

In addition to the authentication problem, it is often the case that the Corporate Proxy will not be able to resolve development servers proxy addresses. This is equivalent to do not use proxy for these addresses that you can set in IE / Firefox.

This can be solved using a local Apache Webserver , acting as a proxy. The relevant extract from Apache.conf is below: 

# Turn on the proxy
ProxyRequests On
 
# which addresses will bypass the normal corporate IP Resolution
ProxyRemote * http://localhost:9999
NoProxy http://localhost:8080 http://localhost:80 etc
Retrieved from "http://www.firstpartners.net/kb/index.php/Windows_Proxy_to_Use_tools_such_as_Lynx%2C_Deploy_on_Corporate_Network"
Personal tools