如何为WireMock多服务配置对应代理URL以转发未匹配请求？

Great question! Your current setup works, but we can streamline it to be more maintainable and scalable—especially if you add more services down the line. Here are a few better approaches:

1. 集中式路由匹配（推荐） #

Instead of maintaining 5 separate high-priority files, create one (or a small set of) stub mapping files that route requests to the correct backend based on request attributes like path prefixes or Host headers. This keeps all your proxy rules organized in one place and avoids redundant configuration.

Example JSON Stub Mapping #

Create a file like multi-service-proxy.json with entries for each service, and set a low priority (higher numeric value, since WireMock uses lower numbers for higher priority) so your custom virtualized stubs take precedence:

{
  "mappings": [
    {
      "request": {
        "method": "ANY",
        "urlPattern": "/service-a/.*"
      },
      "response": {
        "proxyBaseUrl": "https://real-service-a.example.com"
      },
      "priority": 10
    },
    {
      "request": {
        "method": "ANY",
        "urlPattern": "/service-b/.*"
      },
      "response": {
        "proxyBaseUrl": "https://real-service-b.example.com"
      },
      "priority": 10
    },
    // Add entries for services C, D, E here
  ]
}

With this setup, any request starting with /service-a/ that doesn't match a custom virtualized stub will automatically forward to the real Service A URL—and the same logic applies to other services.

2. 动态环境变量配置（适合CI/CD场景） #

If you need to switch between different backend environments (dev, staging, production) without editing stub files, use environment variables in your proxy mappings. WireMock supports interpolating environment variables directly in JSON files.

Example with Environment Variables #

Create a proxy-template.json file:

{
  "mappings": [
    {
      "request": {
        "method": "ANY",
        "urlPattern": "/service-a/.*"
      },
      "response": {
        "proxyBaseUrl": "${SERVICE_A_URL}"
      },
      "priority": 10
    },
    {
      "request": {
        "method": "ANY",
        "urlPattern": "/service-b/.*"
      },
      "response": {
        "proxyBaseUrl": "${SERVICE_B_URL}"
      },
      "priority": 10
    }
  ]
}

Then start WireMock with the environment variables set:

SERVICE_A_URL=https://real-service-a.example.com SERVICE_B_URL=https://real-service-b.example.com wiremock --port 8080 --root-dir ./stubs

This makes your configuration portable across environments without changing the stub files themselves.

3. 路径重写（如果需要调整请求路径） #

If your WireMock endpoint paths don't exactly match the real service paths, use the proxyUrlPrefixToRemove option to rewrite paths before forwarding. For example, if WireMock receives /service-a/api/users but the real service expects /api/users:

{
  "request": {
    "method": "ANY",
    "urlPattern": "/service-a/.*"
  },
  "response": {
    "proxyBaseUrl": "https://real-service-a.example.com",
    "proxyUrlPrefixToRemove": "/service-a"
  },
  "priority": 10
}

Key Note on Priority #

Make sure your proxy mappings have a lower priority (higher number) than your custom virtualized stubs. WireMock processes stubs in order of ascending priority number, so your virtualized stubs (e.g., priority 1) will match first, and only un-matched requests will fall through to the proxy rules (priority 10). This aligns perfectly with your goal of forwarding only un-matched requests to real services.

内容的提问来源于stack exchange，提问作者Ram