You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I could not find anything similar for Quarkus. I even have the feeling that Quarkus is not capable for such a thing right now as it seems that the id of an endpoint is interpreted as path + method + mime-type.
Is there a way I can define a REST endpoint twice and using a header value as selector?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
We are building a versioned api. As it is not public, we would like to avoid a version number in the url.
Also we do receive a header from our clients with the current version running, therefor, I would rather use the header value for endpoint matching.
Spring has a build in its method mapping: https://docs.spring.io/spring-framework/reference/web/webmvc/mvc-controller/ann-requestmapping.html#mvc-ann-requestmapping-params-and-headers
I could not find anything similar for Quarkus. I even have the feeling that Quarkus is not capable for such a thing right now as it seems that the id of an endpoint is interpreted as path + method + mime-type.
Is there a way I can define a REST endpoint twice and using a header value as selector?
e.g.
Beta Was this translation helpful? Give feedback.
All reactions