Errors with v2's reverse_proxy to remote domain

Help
3

Hi @francislavoie, thank you for your reply. I’ve made the suggested adjustments and now receive a response!

Now for the request the response comes via a redirect. Is it possible to do this without the redirect being passed to the client? That way I can cache the response I want. These topics may be related,

I did not notice any redirect happening with the Caddy v1 configuration. Here is the updated config,

services:
  caddy:
    image: caddy:2.3.0
    depends_on:
    - "graphql-engine"
    restart: always
    ports:
    - "80:80"
    - "443:443"
    volumes:
    - ./Caddyfile:/etc/caddy/Caddyfile
    - caddy_data:/data
    - caddy_config:/config
volumes:
  db_data:
  caddy_data:
  caddy_config:

api.revddit.com {
    tls internal
    handle_path /q/* {
        reverse_proxy 172.17.0.1:9090
    }
}

rviewit.com {
    tls internal
    handle_path /api/short/modlogs/* {
        header Access-Control-Allow-Origin *
        reverse_proxy modlogs.fyi {
            header_up Host {http.reverse_proxy.upstream.hostport}
        }
    }
    handle_path /api/short/* {
        reverse_proxy 172.17.0.1:8383
    }
    handle_path /api/long/* {
        reverse_proxy 172.17.0.1:8383
    }
    handle_path /api/* {
        reverse_proxy 172.17.0.1:8383
    }
}