Commented Unassigned: MAJOR Issue with MVC 5.1/ Web API + Jquery [1664]

As of the 5.1 update you've introduced a serious issue in to Request.CreateResponse.

If you return Request.CreateResponse(HttpStatusCode.OK) (or Accepted or any other success code) and the jquery ajax call is setup something like this:

```
$.ajax({
type: "PUT",
url: url,
dataType: "json",
data: value == null ? null : JSON.stringify(value),
contentType: "application/json; charset=utf-8",
```

even though Request.CreateResponse is returning OK it will fail.

And before you say don't set the dataType to json if it isn't expecting a json response, lots of us have a lot of code that is generic for calling web api, and this isn't feesible because it would then have to know if it should be getting a value response back or not.

Web API used to return "no content" in the headers in the above CreateResponse example with no value, as it should. It now is not.

I would classify this as a massively breaking change that needs to be fixed ASAP and a public stable point release produced to fix it.
Comments: Hi, Could you please share the Web API code that you are using and also traces of the raw Request and Response? I haven't tried exactly your scenario about using JQuery to make request...but from what I noticed Web API behaves correctly for the following scenarios: 1. Returns response with status code of 200 OK & 202 Accepted ``` public HttpResponseMessage Get(int id) { return Request.CreateResponse(HttpStatusCode.OK); } public HttpResponseMessage Get(int id) { return Request.CreateResponse(HttpStatusCode.Accepted); } ``` 2. Returns 204 No Content as the action returns void. ``` public void Put(int id, [FromBody]string value) { //do something } ```