I would like to introduce a feature request for Zuul proxy routing. I believe that I would be quite common to have use case when you wish to redirect the user to specific Eureka discovered service, but including some additional context path.
Currently only by specifing the 'url' attribute it's possible to specifiy the specific context paths i.e.:
user:
path: /user/**
url: http://localhost:9999/uaa/user
What I would like to also be able to do is to specify custom context path together with serviceId:
For instance the config could look at fallows:
user:
path: /user/**
serviceId: auth-service
servicePath: uaa/user
There is also ralated issue that would have to be addressed: spring-projects/spring-hateoas#367 - to fix it would require to give user more control of X-Forward-Prefix header.
I would like to introduce a feature request for Zuul proxy routing. I believe that I would be quite common to have use case when you wish to redirect the user to specific Eureka discovered service, but including some additional context path.
Currently only by specifing the 'url' attribute it's possible to specifiy the specific context paths i.e.:
What I would like to also be able to do is to specify custom context path together with serviceId:
For instance the config could look at fallows:
There is also ralated issue that would have to be addressed: spring-projects/spring-hateoas#367 - to fix it would require to give user more control of
X-Forward-Prefixheader.