You have this "CONFIG proxy.config.url_remap.remap_required INT 0" This means requests go through even if there is no matching remap rule. Therefore a request to 127.0.0.1:80 will go through, and connect back to ATS, thereby creating a loop. If ATS is running on a host with address 172.16.0.1 and a request for that address arrives, exactly the same thing will happen. This may be what using your private IP address is doing.
Because the remap rule is for port 80, requests to other ports on localhost or 127.0.0.0/8 will also loop, e.g. HTTPS requests (port 443). On Tue, Apr 14, 2020 at 1:35 PM Kamil <[email protected]> wrote: > Yes, localhost. The plan is to use ATS as proxy for S3 bucket. > So it is running as Docker container/k8s Pod where the other Pods/apps are > calling it like: http://ats:80/object > It is not available from the internet. So far it is working only when > called from inside the docker/k8s pod but not from outside the docker/k8s > pod. > regards, > Kamil > > Dnia 14 kwietnia 2020 19:16 juergenp [core] <[email protected]> napisał(a): > > Hello, > > > > localhost ?? you should provide an existing hostname. localhost points > always to 127.0.0.1. > > this is a loopback interface. > > > > > > > > furthermore a slash is missing at the end of all the urls. > > > > map http://replace_it_with_a_real_hostname <http://localhost/>/ > http://bucket_name.s3.eu-west-1.amazonaws.com/ @plugin=s3_auth.so > @pparam=--config @pparam=s3_auth_v4.config > > reverse_map http://bucket_name.s3.eu-west-1.amazonaws.com/ > http://replace_it_with_a_Real_hostname/ <http://localhost/> > > > > kr > > Juergen > > >
