On 17/11/17 03:57, tappdint wrote:
I was able to get the proxy to work properly with the original settings I
posted. The issue was with the docker network. There were multiple networks
and the squid container ran on a separate network rather than the network
where all the containers were operatin
I was able to get the proxy to work properly with the original settings I
posted. The issue was with the docker network. There were multiple networks
and the squid container ran on a separate network rather than the network
where all the containers were operating. To fix the issue I simply ran squi
On 15/11/17 04:19, tappdint wrote:
Amos Jeffries wrote
You need to either;
* configure the VM running Squid to use a DNS resolver that knows what
the internal domains are, or
* configure the DNS resolver it is using to know those internal
hostnames, or
* configure your network using
Amos Jeffries wrote
> You need to either;
>
> * configure the VM running Squid to use a DNS resolver that knows what
> the internal domains are, or
>
> * configure the DNS resolver it is using to know those internal
> hostnames, or
>
> * configure your network using the standardized .loc
On 14/11/17 11:21, tappdint wrote:
I'm quite new to proxies/networking so I'll try and be as verbose as I can. I
have a VM that will request access to an internal host (dev.abc.com). This
host container and other containers which are dependencies are created
locally on my mac (using docker for ma
I'm quite new to proxies/networking so I'll try and be as verbose as I can. I
have a VM that will request access to an internal host (dev.abc.com). This
host container and other containers which are dependencies are created
locally on my mac (using docker for mac). So I also run a docker squid
cont
