Then your clients are wrong and should be fixed. That is, they are trying to access something other than your S3 bucket via your ATS instance. Based on your description, every request that arrives should have the first line as
GET http://ats-s3-proxy/ HTTTP/1.1 or GET / HTTP/1.1 in both cases with the field Host: ats-s3-proxy If not, why are they connecting to your ATS instance? If so, then the remap rule will prevent the 404 Not Found On Accelerator. On Tue, Apr 14, 2020 at 1:48 PM Kamil <[email protected]> wrote: > Hi Alan, > If I change CONFIG proxy.config.url_remap.remap_required INT to 1 then I > am getting: "Not found on Accelerator" error on any client calling it. > regards, > > Dnia 14 kwietnia 2020 19:41 Alan Carroll <[email protected]> > napisał(a): > > 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). > > >
