-
Notifications
You must be signed in to change notification settings - Fork 3k
Fix handling of overlapping paths in resteasy-reactive server #50384
New issue
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
base: 3.28
Are you sure you want to change the base?
Conversation
Thanks @TomasHofman! Did this pass CI on your fork? |
Hi @geoand , I was locally running tests in following two modules:
and those did pass. I was hoping to get more coverage here on the PR. Now as I reread the contributors file I will get GH actions working on my fork and let you know 👍 (it's been few years since I last contributed here). |
@geoand actually the CI on my fork had run, and looks green (if you can access here? https://github.com/TomasHofman/quarkus/actions/runs/18191107425) |
.body(equalTo("Foo bar_value")); | ||
} | ||
|
||
// TODO: remove this test before commit |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I assume this need to be removed :)
Cool! In that case, feel free to take it out of draft when you are done |
@geoand sure, I will take bit more time, I'm looking at one more touch point. |
Thanks! No rush |
This improves the path matching logic in resteasy-reactive server. It fixes the case when there are overlapping path templates registered, such as:
and the incoming request has path
/path/foo/bar_something
. The expectation is that this path should be matched by the first template. The current behavior however is that server returns 404.