Support Custom Http Routes + URI path parameters
See original GitHub issueCurrently only query string parameters like /api/foo?id=7
are supported. It would be nice if it supported URI path parameter binding also like /api/foo/7
. Some RESTful services go further for things like /api/foo/7/bar/15, so some sort of arbitrary path-to-param mapper would be ideal, but personally I’ve never used that so just an ID would suffice for myself…
I arrived here from Stack Overflow
Issue Analytics
- State:
- Created 7 years ago
- Reactions:2
- Comments:8 (4 by maintainers)
Top Results From Across the Web
custom http route for an API POST without URI parameter
I suppose you don't have controller with proper action method for this URL. Try to add such controller with default route configuration.
Read more >Attribute Routing in ASP.NET Web API 2
This topic discusses how to enable attribute routing in ASP.NET Web API 2 and describes various options for attribute routing.
Read more >Working with routes for HTTP APIs
Routes direct incoming API requests to backend resources. Routes consist of two parts: an HTTP method and a resource path—for example, GET /pets...
Read more >Different approaches to HTTP routing in Go
Compares various routing techniques in Go, including five custom approaches and three using third-party routing libraries.
Read more >Using parameters in routes
Parameters can be used to pass dynamic values from the URI to the controller.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
any progress on this? its a feature I currently need
Yeah I agree, this is a feature currently needed. We are using workaround and placing a layer in-front of functions for now.