Spring Cloud Gateway 2.0如何正确转发带{id}的路径变量？

Hey there! Let's tackle that frustrating issue where your /users/{id} requests keep getting forwarded to /users instead of the correct endpoint on your microservice running at port 8080. I've run into similar quirks with the Finchley version of Spring Cloud Gateway, so here's what you need to check and fix:

1. Check Your Route Predicate Configuration #

First, make sure your route is actually matching the /users/{id} path correctly. A common mistake is using a too-restrictive predicate that only catches /users but not its subpaths.

Bad Configuration (Only Matches /users) #

spring:
  cloud:
    gateway:
      routes:
        - id: user-service
          uri: http://localhost:8080
          predicates:
            - Path=/users

Correct Configuration (Matches /users and /users/{id}) #

You have two solid options here:

• Explicitly list both paths:

  spring:
    cloud:
      gateway:
        routes:
          - id: user-service
            uri: http://localhost:8080
            predicates:
              - Path=/users,/users/{id}
  

• Use a wildcard to match all subpaths under /users (great if you might add more endpoints later like /users/{id}/profile):

  spring:
    cloud:
      gateway:
        routes:
          - id: user-service
            uri: http://localhost:8080
            predicates:
              - Path=/users/**
  

2. Fix RewritePath Filter (If You're Using It) #

If you added a RewritePath filter to modify the request path before forwarding, double-check that it's not stripping out the {id} variable. This is the most common culprit for your issue.

Bad Filter (Strips All Subpaths) #

filters:
  - RewritePath=/users/(?<segment>.*), /users

This rewrites every request starting with /users/ to just /users, which is why your /users/123 ends up at /users.

Correct Filter (Preserves the Path Variable) #

Update the filter to retain the captured segment:

filters:
  - RewritePath=/users/(?<segment>.*), /users/${segment}

3. Avoid Accidental Path Truncation with StripPrefix #

If you're using the StripPrefix filter, ensure it's not removing too many path segments. For example, if your gateway path is /api/users/{id} and you set StripPrefix=1, it will forward to /users/{id} (which is correct). But if you set StripPrefix=2, it would forward to /{id}—which your microservice doesn't handle, and might default to /users if you have a catch-all.

4. Debug the Forwarding Behavior #

To confirm what's happening under the hood, enable debug logging for Spring Cloud Gateway. Add this to your application.yml:

logging:
  level:
    org.springframework.cloud.gateway: DEBUG

You'll see detailed logs showing the incoming path, how it's matched, and the final path sent to your microservice. This is super helpful for spotting any unexpected path modifications.

If you're using Java-based route configuration instead of YAML, here's the equivalent working setup:

@Bean
public RouteLocator customRouteLocator(RouteLocatorBuilder builder) {
    return builder.routes()
            // Matches /users and all subpaths like /users/{id}
            .route("user-service", r -> r.path("/users/**")
                    .uri("http://localhost:8080"))
            .build();
}

Give these changes a try—your /users/{id} requests should now correctly forward to the corresponding microservice endpoint!

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