Spring cloud gateway returns empty response

When encountering an empty response from Spring Cloud Gateway, it's crucial to examine the application's exposed endpoint and the redirect path. By default, Spring Cloud Gateway redirects Uris as they are, potentially leading to an infinite redirect loop.

To rectify this issue, consider employing the RewritePath filter. This filter enables the redirection of product-service/** to /** of product-service. An example configuration:

spring:
  cloud:
    gateway:
      routes:
        - id: product_service
          uri: localhost:5861/
          predicates:
            - Path=/product-service/**
          filters:
            - RewritePath=/product-service/(?<segment>/?.*),$\{segment}

Alternatively, a simpler solution is to update the route configuration to directly point to /product:

spring:
  cloud:
    gateway:
      routes:
        - id: product_service
          uri: http://localhost:5861/
          predicates:
            - Path=/product

By implementing these adjustments, the gateway should function as intended, avoiding empty responses and ensuring smooth request routing.