Hi guys, I am trying to proxy some requests throug...
# general
r
Hi guys, I am trying to proxy some requests through wiremock, but for some reason it doesn't hit the target service and returns a
500
any clue why it would do this ?
Copy code
pti-infra-wiremock-opensanctions-1  | 2023-01-25 21:15:20.211 Proxying: POST <http://localhost:1234/match/default>
pti-infra-wiremock-opensanctions-1  | 2023-01-25 21:15:20.246 Request received:
pti-infra-wiremock-opensanctions-1  | 172.18.0.22 - POST /match/default
pti-infra-wiremock-opensanctions-1  | 
pti-infra-wiremock-opensanctions-1  | Accept: [text/plain, application/json, application/cbor, application/*+json, */*]
pti-infra-wiremock-opensanctions-1  | Connection: [keep-alive]
pti-infra-wiremock-opensanctions-1  | User-Agent: [okhttp/4.9.3]
pti-infra-wiremock-opensanctions-1  | Host: [wiremock-opensanctions:8080]
pti-infra-wiremock-opensanctions-1  | Accept-Encoding: [gzip]
pti-infra-wiremock-opensanctions-1  | Content-Length: [86]
pti-infra-wiremock-opensanctions-1  | Content-Type: [application/json;charset=UTF-8]
pti-infra-wiremock-opensanctions-1  | {"queries":{"q1":{"schema":"Person","properties":{"name":"John Smith","address":[]}}}}
pti-infra-wiremock-opensanctions-1  | 
pti-infra-wiremock-opensanctions-1  | 
pti-infra-wiremock-opensanctions-1  | Matched response definition:
pti-infra-wiremock-opensanctions-1  | {
pti-infra-wiremock-opensanctions-1  |   "status" : 200,
pti-infra-wiremock-opensanctions-1  |   "proxyBaseUrl" : "<http://localhost:1234>"
pti-infra-wiremock-opensanctions-1  | }
pti-infra-wiremock-opensanctions-1  | 
pti-infra-wiremock-opensanctions-1  | Response:
pti-infra-wiremock-opensanctions-1  | HTTP/1.1 500
pti-infra-wiremock-opensanctions-1  | (no headers)
and wiremock is setup through docker compose like so :
Copy code
wiremock-opensanctions:
    image: public.ecr.aws/s4w6t4b6/wiremock/wiremock:2.32.0
    networks: [pti]
    hostname: wiremock-opensanctions
    restart: unless-stopped
    volumes:
      - ./wiremock/opensanctions:/home/wiremock
    user: "${UGID}"
    command: --proxy-all="<http://localhost:1234>" --record-mappings
I think I know what's going on, the use of
localhost
inside a docker instance, that won't work
t
Hi @Remi Cartier, yes, localhost would refer to the Docker container’s loopback interface rather than the host’s. You can usually refer to the Docker host via
host.docker.internal
however, so this might be worth trying as your proxy target.
r
👍