This message was deleted.

Hi @Jackie chen, WireMock doesn’t support this unfortunately as it has a single HTTP client instance and thus a single set of proxy settings. The only solution I can think of off the top of my head (short of forking WireMock and customising it in this way) is to put e.g. an nginx instance in front of it to act as a single proxy, then configure this to route to the relevant corporate proxies.

@Tom thank you very much for the idea. This sounds good. Let me try to understand this. 1) initialize wiremock instance with proxyVia(nginx proxy) 2) configure this nginx proxy to route requests to the desired corporate proxy Then requests will be proxied via the desired corporate proxy and sent to the external destination. Is my understanding correct?

Yes, that’s what I had in mind. Let me caveat - I’ve never actually tried this myself!