On 18/06/18 16:54, Kedar K wrote:
> Hi Amos,
> Here is the topology:
>
> client (curl from host running docker) --> squid_child (docker, using
> ssl-bump with intercept) --> squid_parent (VM with internet connection,
> https_port without ssl-bump) --> origin server.
Consider where/how the child
Hi Amos,
Here is the topology:
client (curl from host running docker) --> squid_child (docker, using
ssl-bump with intercept) --> squid_parent (VM with internet connection,
https_port without ssl-bump) --> origin server.
local - 72.19.0.2:443 is the container running squid child
remote - remote=1
On 18/06/18 02:08, Kedar K wrote:
> Hello,
>
> I am hitting this issue when running squid in a docker with ssl parent
> cache_peer.
>
Can you describe that a bit clearer please? An end-client, two proxies
and origin server makes four HTTP agents involved with this traffic.
Which of those proxi
Hello,
I am hitting this issue when running squid in a docker with ssl parent
cache_peer.
Host header forgery detected on local=11 72.19.0.2:443 remote=
172.19.0.1:44522 FD 15 flags=33 (local IP does not match any domain IP)
The host ip of the docker would not resolve to a domain. How to
work-a
