Corporate Proxies

Setting up for accessing files on via Corporate Proxy

It has been reported that you may run into issues within a virtual private cloud sending http requests to/from your docker containers.

You may be in a situation where you need to access an externally hosted SPA. (On AWS S3 perhaps). You may run into trouble trying to send http requests from your Corporate VPC with the containers to through your router. (Particularly if it is a Microsoft router that requires a username and password in the URL - which Chrome doesn't support.)

The solution in this case was solved by using [node-http-proxy]|(https://github.com/nodejitsu/node-http-proxy) - simply pass your http basic credentials to node-http-proxy on startup, then point Chrome to this proxy running locally.