Public and Private API Definitions in Spring Cloud Gateway: Static or Database-Driven?
I am using Spring Cloud Gateway and have implemented a RouteValidator class to secure my APIs. Currently, I define the public and private APIs statically in the code, like this:
Error creating bean with name ‘scopedTarget.eurekaApplicationInfoManager’
Trying to run spring cloud gateway in AWS fargate and encountering below issue.
JDK 17,
Spring boot 3.1.2
Below is the log.
Spring cloud gateway : Returns 200 to an api call but no response in body
When I hit URL through postman, [localhost:8090/api/v1] I get 200 but no response in body and when I check the logs of the service which was hit through gateway it shows nothing, which means it didn’t even came to the service.(So it should show 404 right?)
Also there is one more issue that I am not sure where am I doing wrong
when I use spring.cloud.gateway.routes[0].uri=localhost:6002 it gives 200 but
when I use spring.cloud.gateway.routes[0].uri=http://localhost:6002 it gives 404 in logs,
But point to be noted when I hit it through postman I get 200 for any above mentioned ways.
Converting ServerHttpRequest to HttpServletRequest
I’m migrating an application from Netflix/Zuul to Spring Cloud Gateway: