The spec shows that an XHR request only sends the OPTIONS pre-flight request with some content-types. It does not send an OPTIONS request with application/x-www-form-urlencoded but does with form-data or raw JSON. This knowledge can save a lot of pain when trying to call an MVC endpoint with an

Using in-memory server [TestMethod] public void Get() { var client = new HttpClient(); var request = new HttpRequestMessage { RequestUri = new Uri("http://localhost/api/hello"), Method = HttpMethod.Get }; request.Headers.Accept.Add(new MediaTypeWithQualityHeaderValue("application/json")); using (var response = client.SendAsync(request).Result) {

Swagger is great for documenting APIs. Using an IHttpActionResult return type, however, means that Swagger does not know the data structure that will be returned: The fix Decorating the controller action method with the below ensures that Swagger is aware of the context. [System.Web.Http.Description.ResponseType(typeof(IEnumerable&

Swagger is great for documenting APIs, and installs easily via Nuget. However, it can be problematic over https, with an error "Can't read from server. It may not have the appropriate access-control-origin settings.". The solution The page is being loaded with the https:// protocol, however, Swagger