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
Describe the bug
A dynamic /{path} endpoint with a static /bar endpoint works fine. But if I add another one with /baz, requests to routes with a /ba prefix fail. This also occurs with other prefixes and if the static routes consist of more URL segments.
# Windows Power Shell:
docker pull devopsfaith/krakend@1.4.1
docker run -p 8080:8080 -v ${PWD}:/etc/krakend/ devopsfaith/krakend:1.4.1
# in another terminal:
curl http://localhost:8080/basomething
Expected behavior
I would expect /basomething to match the /{path} endpoint.
Additional context
I know the documentation states that colliding routes are not supported. But according to #325 it should work and there are no errors at startup.
The text was updated successfully, but these errors were encountered:
Hi @mathisuniversal, the documentation says that you cannot have colliding routes and until KrakenD 2.0 this statement won't be removed from the documentation.
Although you can declare colliding routes on 1.4.1, they are still officially unsupported and there will be problems with endpoints sharing prefixes, as you have pointed out. See this issue: gin-gonic/gin#2959
Krakend 2.0 will either fix, document or provide a workaround to this issue.
This issue was marked as resolved a long time ago and now has been automatically locked as there has not been any recent activity after it. You can still open a new issue and reference this link.
Describe the bug
A dynamic
/{path}
endpoint with a static/bar
endpoint works fine. But if I add another one with/baz
, requests to routes with a/ba
prefix fail. This also occurs with other prefixes and if the static routes consist of more URL segments.Your configuration file
Minimal example:
Commands used
How did you start the software?
Expected behavior
I would expect
/basomething
to match the/{path}
endpoint.Logs
Additional context
I know the documentation states that colliding routes are not supported. But according to #325 it should work and there are no errors at startup.
The text was updated successfully, but these errors were encountered: