Exposed REST API (/greeting) can be called, by calling the /test api of the deployed Zuul Service:
zuul:
routes:
users:
path: /test/**
write here the route of the called Rest API, GET /greeting is the URL.
url: http://example.com/greeting
Despite of, connected in ssh in the pod, the Zuul service container was able to reach the /greeting API, once called through Zuul it seems not be able to resolve the url.
Please find error log in attachment.
Same url, with Unirest client was instead callable.
I’ve created a Filter – UniRestSimpleHostRoutingFilter which used behind a Unirest Client in order to make the call and in this way call is correctly forwared.
There’s a way in order to make it works without defining a new Filter, maybe some properties that by default make it not works correctly?
I’ve tried to deploy under OpenShift Container Platform a project in order to test Zuul under OpenShift.
Code can be found here: https://github.com/aleMessoMale/zuul-poc.git
It only tries to call a rest service exposed by another microservice (J2EE Spring Boot) whose code can be found here: https://github.com/aleMessoMale/gs-rest-service.git
Exposed REST API (/greeting) can be called, by calling the /test api of the deployed Zuul Service: zuul: routes: users: path: /test/**
write here the route of the called Rest API, GET /greeting is the URL.
Despite of, connected in ssh in the pod, the Zuul service container was able to reach the /greeting API, once called through Zuul it seems not be able to resolve the url.
Please find error log in attachment.
Same url, with Unirest client was instead callable.
I’ve created a Filter – UniRestSimpleHostRoutingFilter which used behind a Unirest Client in order to make the call and in this way call is correctly forwared.
There’s a way in order to make it works without defining a new Filter, maybe some properties that by default make it not works correctly?
Thank you, zuul-error.log