In Mozilla Firefox, you can see the same through: about:preferences#advanced In Google Chrome, you might be able to access this settings page: chrome://net-internals/#proxy If you can directly see the proxy settings through any of the above, then you’re done, there’s probably no need to look further just grab the hosts/ips/ports.Īnother way if you’re on Windows 10 is to look at the Proxy settings through the Settings app of the OS, as described here: (that the article also covers how to discover the proxy settings for OSX & Linux). To reach that screen, you can look at this Microsoft KB article: You’ve probably already seen this Window at least once in your life -) Some “basic” environments simply enforce a proxy (or set of proxies) through the system configuration (usually defined/enforced through group policies and the like in Windows environments), which can be checked out through Internet Explorer (meh): Some ways to find out which proxies are used

If you know what you’re doing, then keep on reading.

In any case, make sure to reach out to the security and network teams to see if there are established/accepted solutions to let you do what you want. And usually I want my tools to be doing that or at least to be able to do it from a terminal. Personally, I’ve often needed Web access to be able to download certain tools / download npm/maven/whatever packages, etc. Another one, more valid could be to be able to access the Web from your development tools and/or terminal. The first one might be curiosity, which may be the worst reason. There are multiple reasons for which you might want to know more about the corporate proxies being used. If you’re not sure, then ask the network / security team / CISO before doing anything that could put you in a bad spot. Make sure that you’re not doing something that goes against those policies. Why and a little warningįirst of all, a word of advice: there are often strict security policies in place around network traffic in general. In more complex environments, you’ll need to analyze the pac file to find those out. Finally, I’ll tell you how to configure your apps and command-line tools access the Web.Īs we’ll see, in basic environments, you’ll just have to look at the settings to find the URLs/IPs/ports of the proxies. I’ll also mention how more complex IT environments handle proxy settings using the automatic proxy discovery protocol (WPAD) and pac files, perform TLS termination and sometimes even only allow specific user-agents through. In this article I’ll give you a few tips about how to discover which proxy/proxies is/are used (if any).

Npm config set noproxy