title: Nuget behind Corporate proxy - External sources work, but internal does not
body: <p>So in order to use NuGet and other dev tools working inside my organisation we've had to set a system wide environment variable 'http_proxy' for each user in our user specific Environment variables.</p>
  
  <p>Now, this works for everything we've tried so far, all package managers like NuGet, NPM, chocolatey, all work fine with external repositories.</p>
  
  <p>Recently we've tried to set up an internal NuGet server on our build server to internally host common packages. Everyone can browse to the URL where the server is located: <code>-ip-/nuget</code> and we can see the XML feed. The issue comes when we try to use nuget.exe, or Visual Studio 2017 for connecting to this source, the requests to find packages all time-out after <code>100000ms</code> which i guess is the default timeout.</p>
  
  <p>We can also browse exactly to the URL that times out out in any browser with no issue. I'm assuming that this is something to do with our internal proxy trying to route traffic out of the network when it is actually internal, but i have no way of verifying that.</p>
  
  <p>Is there anything we can try to see if we can get this resolved?</p>