We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Imagine your gateway has also a @RestController and serves GET /user
GET /user
At the same time you have a route, which will check the request with some predicates (this could be for auth) on GET /some-prefix/user
GET /some-prefix/user
Is there a smart way to 'disable' the controller for unwanted access?
I guess that's just not possible without splitting the rest controller functionality into another service and point to it.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Imagine your gateway has also a @RestController and serves
GET /user
At the same time you have a route, which will check the request with some predicates (this could be for auth) on
GET /some-prefix/user
Is there a smart way to 'disable' the controller for unwanted access?
I guess that's just not possible without splitting the rest controller functionality into another service and point to it.
The text was updated successfully, but these errors were encountered: