-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
non-wildcard and wildcard router conflict, why? #210
Comments
I have the same problem, looking the issues history, other peoples pointed this problem years ago, but have never fixed =/. |
Me too.
I also use
|
I guess |
I have an even stranger conflict: router.GET("/:room/:screen/up", handler) I cannot fathom how this could be a conflict, since /socket would not match the pattern of the first route, since it misses part of the path. |
For anyone else looking for a solution, https://godoc.org/github.com/dimfeld/httptreemux solves this problem, why it wasn't contributed back I am not sure though. |
Duplicate of #183 |
The text was updated successfully, but these errors were encountered: