Yes, it is possible. You (like most people) are being thrown by Microsoft’s marketing of Action Filter Attributes, which are conveniently put into a single class, but not at all DI-friendly. The solution is to break the Action Filter Attribute into 2 parts as demonstrated in this post: An attribute that contains no behavior to … Read more
The Ninject.Web.WebApi NuGet package has just been released. From now on the preferred solution is using that package. I couldn’t find any related documentation but after installing the package everything worked for me. Install-Package Ninject.Web.WebApi After installation both the normal MVC and the API controller instances are provided by Ninject. If you have Ninject.Web.Common already … Read more
Updated 4/28/2015 You could create a custom provider based on MultipartFormDataRemoteStreamProvider. Example: public class CustomMultipartFormDataProvider : MultipartFormDataRemoteStreamProvider { public override RemoteStreamInfo GetRemoteStream(HttpContent parent, HttpContentHeaders headers) { return new RemoteStreamInfo( remoteStream: new MemoryStream(), location: string.Empty, fileName: string.Empty); } } Updated Custom In-memory MultiaprtFormDataStreamProvider: public class InMemoryMultipartFormDataStreamProvider : MultipartStreamProvider { private NameValueCollection _formData = new NameValueCollection(); private … Read more
This kind of scenario is not well supported by the standard routing methods. You may want to use attribute based routing instead as this gives you a lot more flexibility. Specifically look at the route constraints where you can route by the type: // Type constraints [GET(“Int/{x:int}”)] [GET(“Guid/{x:guid}”)] Anything else will turn into a bit … Read more
Attribute routes cannot be inherited. This was a deliberate design decision. We didn’t feel right and didn’t see valid scenarios where it would make sense to inherit them. Could you give a more realistic scenario as to where you would want to use this? [Update(3/24/2014)] In the upcoming 5.2 release of MVC Web API, there … Read more
We ran into this problem because we had set up CORS according to best practice (e.g. http://www.asp.net/web-api/overview/security/enabling-cross-origin-requests-in-web-api) AND ALSO had a custom header <add name=”Access-Control-Allow-Origin” value=”*”/> in web.config. Remove the web.config entry, and all is well. Contrary to @mww’s answer, we still have EnableCors() in the WebApiConfig.cs AND an EnableCorsAttribute on the controller. When we … Read more
Look at what I have found! Add in some custom headers inside <system.webServer>. <httpProtocol> <customHeaders> <add name=”Access-Control-Allow-Origin” value=”*” /> <add name=”Access-Control-Allow-Methods” value=”GET, POST, OPTIONS, PUT, DELETE” /> </customHeaders> </httpProtocol> Then I can do the CORS authentication.
When the ASP.NET Web API calls a method on a controller, it must set values for the parameters, a process called parameter binding. By default, Web API uses the following rules to bind parameters: If the parameter is a “simple” type, Web API tries to get the value from the URI. Simple types include the … Read more
The IMDb has a public API that, although undocumented, is fast and reliable (used on the official website through AJAX). Search Suggestions API https://sg.media-imdb.com/suggests/h/hello.json https://v2.sg.media-imdb.com/suggests/h/hello.json (as of 2019) Format: JSON-P Caveat: It’s in JSON-P format, and the callback parameter can not customised. To use it cross-domain you’ll have to use their function name for the … Read more