asp.net-web-api-routing

问题 I am using Asp.Net WebAPI for a project. I am currently working on authentication and authorization. I have a messageHandler that will check the HTTP authentication header of a request and build my identity and user profile. However, I want to annotate my controller action (or just the controller) with claims that the action may require (we have a lot of claims that a user can have, so I don't want to load them all). e.g.: public class MyController : ApiController { [LoadClaims("SomeClaim",

问题 I've some classes like CustomerModel or CustomerDetailsModel which are inherting from ModelBase . Also i don't want to introduce subclasses for each modeltype. In one case have a post method foreach. So i could manually create multiple routes to call a method which looks like Handle<T>(T model) where T : ModelBase They only differ in the path the were called. For example: baseurl/api/customer => CustomerModel baseurl/api/customerdetails => CustomerDetailsModel I want to implement a generic

问题 Background/Context: We have two routes, with different route prefixes: Route 1 prefix: /api Route 2 prefix: /api/partial Currently, we use the same EdmModel for both route prefixes. (See the first code snippit, named "What we currently do"). What we want: We need to only allow a subset of API functionality for Route 2: /api/partial . We want to return 404 when someone tries to access an API that is not available to the "partial" EdmModel Example: We want to return 404 for /api/parial/products

问题 Is it possible to customize ASP.NET Web API's routing mechanism to route all requests to the API to one controller method? If a request comes in to www.mysite.com/api/products/ or www.mysite.com/api/otherResource/7 All would be routed to my SuperDuperController's Get() method? 回答1: I ran into a case where I needed to do this. (Web API 2) I first looked into creating custom IHttpControllerSelector and IHttpActionSelector s. However, that was a bit of a murky way around. So I finally settled on

问题 ASP.NET MVC4 Web API v1 controller is defined below. It should accept 1 or 2 query string parametrs. However ko parameter is always null if method is called. Request is below. How to fix so that klient or namepart parameter can passed in query string ? Web API v1 controller: namespace MyApp.Controllers { public class CustomersSearchViewModel { public string Klient { get; set; } public string Namepart { get; set; } } [Authorize] public class CustomersController : ApiController { public

问题 I'm trying to get this to work: [Route("api/Default")] public class DefaultController : ApiController { [HttpGet, Route("{name}")] public string Get(string name) { return $"Hello " + name; } } by calling this http://localhost:55539/api/Default?name=rami but not working, tried this also: http://localhost:55539/api/Default/Hello?name=rami , Also this not working: http://localhost:55539/api/Default/Hello/rami 回答1: Make sure attribute routing is enabled in WebApiConfig.cs config

问题 I'm following the article on Attribute Routing in Web API 2 to try to send an array via URI: [HttpPost("api/set/copy/{ids}")] public HttpResponseMessage CopySet([FromUri]int[] ids) This was working when using convention-based routing: http://localhost:24144/api/set/copy/?ids=1&ids=2&ids=3 But with attribute routing it is no longer working - I get 404 not found. If I try this: http://localhost:24144/api/set/copy/1 Then it works - I get an array with one element. How do I use attribute routing

问题 I've been playing with the new Web API 2 (which looks very promising btw) but I'm having a bit of a headache to get some routes working. All works fine when I have GetAllUsers / GetUser(int id), but then when I add GetUserByName(string name) and/or GetUserByUsername(string username) things start to be creepy. I know that the int will be the first one and that I can re-order the routes but let's imagine the following scenario: A user can have a valid username=1234 or name=1234 (I know it's

问题 Was wondering if it was possible to have more than one route pointing to a WebApi controller? For example I will like to have both http://domain/calculate and http://domain/v2/calculate pointing to the same controller function? 回答1: public static class WebApiConfig { public static void Register(HttpConfiguration config) { // Web API configuration and services // Configure Web API to use only bearer token authentication. config.SuppressDefaultHostAuthentication(); config.Filters.Add(new

问题 Was wondering if it was possible to have more than one route pointing to a WebApi controller? For example I will like to have both http://domain/calculate and http://domain/v2/calculate pointing to the same controller function? 回答1: public static class WebApiConfig { public static void Register(HttpConfiguration config) { // Web API configuration and services // Configure Web API to use only bearer token authentication. config.SuppressDefaultHostAuthentication(); config.Filters.Add(new