The best way to debug this is to enable diagnostic tracing. You can either do that via records.config, or many of us just prefer it from the command line. The tracer to star at with here would be http_hdrs, e.g. from command line (you may have to sudo):
$ ./bin/traffic_server -T http_hdrs Make sure you shutdown the normally running ATS instance if you do this from command line. When enabled via records.config, your debug messages ends up in your log directory, from command line they go straight out to stdout. — Leif > On Jun 23, 2024, at 07:07, Andreas Wederbrand <andr...@wederbrand.se> wrote: > > > Hi! > > I'd like to use ATS to strangle an existing set of services in favour of some > new ones. > > To do that I'd like to move the dns-name to point to ATS but split traffic > between the new services and the old, typically sending some calls back out > to the "outside", our old hosting. > > Typically I'd like for something like this, but obviously not google. > > map /google/ https://www.google.com/ > > I've tried but for some reason it doesn't work. I've configured these 3 > settings > CONFIG proxy.config.url_remap.remap_required INT 1 > CONFIG proxy.config.url_remap.pristine_host_hdr INT 0 > CONFIG proxy.config.reverse_proxy.enabled INT 1 > > I'm getting the correct host from %<cqu> in my logs, but status 404 in > %<sssc>. From the logs in my origin I'm getting nothing at all, leading me to > think the request never really left ATS. > > Am I missing something? Clearly the ATS can't know "inside" from "outside", > right? > > Thanks.
