-
Notifications
You must be signed in to change notification settings - Fork 8k
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
404 when using dynamic routing #2762
Comments
duplicated of #2754 ? |
I don't think it is really duplicated of #2754. It expects that getting '/:cc' when not matching others with using path like '/xx', but it will get 404 actually when we use a path with the common prefix 'a' of '/aa/*xx' and '/ab/*xx'. It seemed the '/:cc' can not work in such cases. |
Just attached a debugger locally to get a sense what's going on. Lines 441 to 448 in 1d0f938
I think instead of a |
Also found this problem, seems it's easy to resolve this problem by checking the Lines 567 to 572 in 1d0f938
But as you said, we need more tests because of this change related to other features like TSR. |
In fact, there are several situationsadd router r.GET("/:cc/cc", newHandler("/:cc/cc")) call /all/cc -> 404 prerequisite:
|
(cherry picked from commit d4ca9a0)
(cherry picked from commit d4ca9a0)
Description
It will bring 404 problem when using dynamic routing(*,:) like below , by calling https://localhost:8080/all. It seemed can not match the path with prefix 'a', such as 'all'.
How to reproduce
Expectations
Actual result
Environment
The text was updated successfully, but these errors were encountered: