Web API Service – How to use “HttpContext.Current” inside async task
I’m using a “Post” async method of webApi rest service:
asp.net-web-api
Asp.Net MVC4 + Web API Controller Delete request >> 404 error
I have a VS2012 MVC4 solution where I test Web API Controllers.
Getting related entities ASP.NET WebApi OData v4 results in “No HTTP resource was found that matches the request URI”
I followed this asp.net tutorial by Mike Wasson, and managed to set up the related entities just fine, but when I applied this logic to my project the more complex entity relations (in that there are more of them; that’s the only difference) wouldn’t succeed in an OData call, I got a 404 with this payload:
How to get Json Post Values with asp.net webapi
i’m making a request do a asp.net webapi Post Method, and i’m not beeing able to get a request variable.
Web Api won’t download file using jQuery Ajax and Basic Auth
I am using the ASP.NET Web API to build a prototype of a web service (and site) which has a method to download a file. When the user on the front-end presses the export button a jQuery ajax GET request is made and received by the controller which on it’s turn calls the method named Excel (shown below). The method runs without any problem and finishes. When I look in Chrome at the header (see https://skydrive.live.com/redir?resid=2D85E5C937AC2BF9!77093) it receives the response with (as far as I am concerned) all the right headers.
How do I dispose of resources after an ASP.NET Web API request completes?
I am attempting to expose an IQueryable<> over ASP.NET Web API and I find that I need to keep the data source open until the request completes, so that the OData query system built into ASP.NET Web API can do its job.
Rewind request body stream
I am re-implementing a request logger as Owin Middleware which logs the request url and body of all incoming requests. I am able to read the body, but if I do the body parameter in my controller is null.
Using DTO’s with OData & Web API
Using Web API and OData, I have a service which exposes Data Transfer Objects instead of the Entity Framework entities.
Can you use the attribute-based routing of WebApi 2 with WebForms?
As the title states, I’m wondering if you can use the attribute-based routing of WebAPI 2 with WebForms. I feel like this can obviously be done given you can use WebAPI2 just fine in a WebForms application… I just can’t figure out how to enable attribute-based routing.
POST data from Android to Web API returns 404
I’m trying to send data from my Android client as a POST request to my Web API Backend but it returns a 404 response code. Here’s my code: