Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

RESTEasy reactive endpoint 404

See original GitHub issue

Describe the bug

When two endpoint with similar URI’s are created, one of them returns 404. Ex: /device-features/{featureId}/permissions /device-features/{featureId}/actions

Expected behavior

Both Endpoints return 200

Actual behavior

No response

How to Reproduce?

https://github.com/victor-costa-avancee/resteasy_path_reproducer

Output of `uname -a` or `ver`

Darwin MBP-de-Vic.localdomain 20.3.0 Darwin Kernel Version 20.3.0: Thu Jan 21 00:06:51 PST 2021; root:xnu-7195.81.3~1/RELEASE_ARM64_T8101 arm64

Output of `java -version`

No response

GraalVM version (if different from Java)

No response

Quarkus version or git rev

2.1.1.Final

Build tool (ie. output of `mvnw --version` or `gradlew --version`)

No response

Additional information

No response

Issue Analytics

State:
Created 2 years ago
Comments:11 (4 by maintainers)

Top GitHub Comments

1reaction

stuartwdouglascommented, Aug 16, 2021

Actually you are completely right, I was thinking about how our implementation was working rather than properly reading the spec (unfortunately the algorithm as described in the spec is super slow, so you can’t just implement it directly).

https://github.com/quarkusio/quarkus/pull/19355 will actually take care of this one as well.

0reactions

victor-costa-avanceecommented, Aug 13, 2021

But shouldn’t Regex(/device-features/{featureId}/permissions) be filtered out in step c) when matching against the request? This is what I understood after looking at the JAX-RS 2.1 spec for the first stage of request matching:

Input U = "/device-features/123/actions"

1.a  E = {}

1.b  Add regular expressions of each root resource to E
       R("/device-features/{featureId}/permissions") = "\/device-features\/([^\/]+?)\/permissions(\/.*)?"
       R("/device-features") = "\/device-features(\/.*)?"
  so E = { "\/device-features\/([^\/]+?)\/permissions(\/.*)?",  "\/device-features(\/.*)?" } 

1.c  Filter E by matching each element against U
  so E = { "\/device-features(\/.*)?" }

1.d  Ignore this step since E isn't empty

1.e  No need to sort since E only has one element

1.f  Rmatch = E[0] = "\/device-features(\/.*)?"
      Rmatch then maps back to the DeviceFeatures root resource, so each of it's endpoints can 
      then be trialed in the future steps