ASP.NET Web API
-
Support OutputCache on WebAPI calls
In ASP.NET MVC it easy to cache the output of a call by applying the outputcache attribute. A similar feature for WebAPI would help for cacheable resources.
65 votes -
Support Nested Routes
MVC has areas, which would work nicely for this. My thoughts behind this are that it's nice to package functionality as modules, and areas serve that purpose well in MVC apps. Of course, it would be nice to be able to host nested areas, as well.
117 votes -
Enhance the routing API
While I was working on WebAPIContrib I found several issues with the Routing API. I described it in more detail here: http://pedroreys.com/2012/03/14/asp-net-web-api-routing-needs-a-hug/
28 votes -
Support Depenedency Injection on MessageHandlers
Support Depedency Injection for MessageHandlers by resolving the message handlers out of the ServiceResolver or providing a MessageHandlerFactory similar to the old WebApiConfiguration.MessageHandlerFactory.
34 votesLet us know if you care about broader dependency injection support by voting for this one.
-
Impovements in ApiExplorer
Right now it's impossible to add documentation of the multipart form data parameters and exclude / rename Model Binder arguments.
38 votes -
9 votes
We are looking at improving our story around PATCH. Vote this one up if you think this is important!
-
Both traditional and verb-based routing cannot be used in the same ApiController
Original discussion here: http://aspnetwebstack.codeplex.com/workitem/184
10 votesWe are looking at having better support for this, in part by making our action selection logic easier to extend.
-
Support OData changesets for batch/unit of work updating
When using REST services in smart clients or rich JavaScript clients, it is normal to cache changes on the client side and send multiple updates back as a batch. Being able to leverage the change sets support in OData for this would be great.
15 votesThank you for this suggestion. We are investigating adding change set support to ASP.NET Web API OData. It won’t make it in for the first release, but we are considering adding change set support in a future version. Please vote if this feature is important to you.
-
Use Reflection to Auto Populate the Allow Header
Based on the current Route being executed, it should be possible to detect HTTP methods the same route supports and therefore populate the Allow header in the response. e.g. whilst performing a GET on /api/values it should be possible to detect that the route supports both GET and POST (in fact the code I presume already has this list so that it knows which Action to call). The Allow header could then be populated with GET, POST.
The icing on the cake would be that the Authorize attribute is still checked so if the caller does not have permission to…
6 votes
- Don't see your idea?
