Seeing "panic: wildcard route conflicts with existing children" unexpectedly about httprouter HOT 11 CLOSED

Intended.
The router matches prefixes, not the complete route at once. /:some and /otherthing conflict obviously. It doesn't matter that no handler is registered for /:some only.

The intention is, that there is only one or none possible route for any prefix when matching incoming requests. But if someone requests /otherthing both the variable-length parameter /:some and the static path /otherthing would match.

from httprouter.

I have the same issue. Take the following example:

a.mux.POST("users/:id/verify", user.Verify)
a.mux.POST("users/activated", user.GetActivatedUsers)

The first verifies one special user while the second returns a collection of activated users based on the request payload.

This is possible with many modern routers so the decision really surprised me.

from httprouter.

I have the same problem as @CodingRogue. Surprisingly, we're both doing something user-related..

users.GET("/new")
users.GET("/:id/edit")

Something like /users/edit/:id instead of /users/:id/edit would work, but I'd really prefer /users/:id/edit.

from httprouter.

I'm afraid this will happen quite often in more complex rest apis. Is there any solution or workaround except switching routers?

from httprouter.

You could probably embed httprouter in a new struct and refine httprouter's methods to support the routes above. But I ended up just replacing httprouter with gorilla/pat. gorilla/pat also has regex matching so you can match numbers.

from httprouter.

I will check out pat then, thanks.

from httprouter.

the routes /users/:id/verify and /users/activated collide. I guess that you have a route like /users/:id to view the profile of user but, what happen if a username is named "activated"? goes to route /users/activated or /users/:id (:id would be "activated")?

httprouter encourages the good route design.

For fix your routes, should look like:

a.mux.POST("user/:id", user.Profile)
a.mux.POST("user/:id/verify", user.Verify)
a.mux.POST("users", user.GetAll)
a.mux.POST("users/activated", user.GetActivatedUsers)

from httprouter.

I can see your point but this route design is not REST compatible. I need to have the same resource identifier reachable through all necessary http verbs (GET, POST, PUT, PATCH, DELETE...).

from httprouter.

But each http verb must do things differently from the rest...

from httprouter.

I hit the same issue. I think this is a pretty common use case, and something I would love to see gin accommodate. You can see similar patterns in GitHub, Twitter, Facebook, etc:

github.com/
github.com/issues
github.com/:user
github.com/:user/:repo

twitter.com/mentions
twitter.com/i/notifications
twitter.com/:username

www.facebook.com/events/upcoming
www.facebook.com/messages/
www.facebook.com/:username

from httprouter.

#73

from httprouter.