HttpResponseMessage(HttpStatusCode.Conflict); returns a web page

Using ApiController.

public HttpResponseMessage Post()

{

return HttpResponseMessage (HttpStatusCode.Conflict);

}

This returns a web page with the classical ASP.NET Conflict content.

If I use

return new HttpResponseMessage<string>("", HttpStatusCode.Conflict);

I get

HTTP/1.1 409 Conflict

Content-Type: application/xml; charset=utf-8

Content-Length: 47

<?xml version="1.0" encoding="utf-8"?><string/>

Any way I can return HttpStatusCode.Conflict without content at all?

Best regards!

Re: HttpResponseMessage(HttpStatusCode.Conflict); returns a web page

I forgot to mention this is with MVC 4 Web Api

Thanks!

Re: HttpResponseMessage(HttpStatusCode.Conflict); returns a web page

Try passing null.

Re: HttpResponseMessage(HttpStatusCode.Conflict); returns a web page

Try:

throw new HttpResponseException(HttpStatusCode.Conflict);

This is what we do for all of our no content status codes.

Re: HttpResponseMessage(HttpStatusCode.Conflict); returns a web page

I tried it already, passing null returns

<?xml version="1.0" encoding="utf-8"?><Stream xsi:nil="true" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>

Re: HttpResponseMessage(HttpStatusCode.Conflict); returns a web page

throw new HttpResponseException(HttpStatusCode.Conflict);

also returns the ASP conflict Web Page.

Re: HttpResponseMessage(HttpStatusCode.Conflict); returns a web page

MVC4 pretends to be a good HTTP handler, but I realize I should stick with WCF. There is too much to overwride with MVC, but WCF is more intuitive.

Re: HttpResponseMessage(HttpStatusCode.Conflict); returns a web page

Try

return new HttpResponseMessage<string>(null, HttpStatusCode.Conflict,
GlobalConfiguration.Configuration.Formatters.Where(x=>x.SupportedMediaTypes.Any(y=>y.MediaType == "application/json")));

I just cannot understand why you do not want to send back any body. Just return some useful information.

Re: HttpResponseMessage(HttpStatusCode.Conflict); returns a web page

Performance issue.

Performance is a key driver with this project. We don't want generate data and transfer through the wire if it's not used.

In this case, I try to create a resource that already exists.

A status code of 409 means

- The resource I am trying to create already exists

- I should use GET, PUT or DELETE to read, modify or delete it.

There is no need for any other detail, and we won't tolerate such overhead.

I am doing an exercise comparing WCF with MVC for REST API . WCF allows me to control my HTTP requests. MVC4 is a model that I find harder and harder fit in REST paradigm, because of all the overhead and the twisted plumbing to manage HTTP requests.

The early documentation about MVC4 Web Api sounds promisisng, and claims to have thinner footprint, but the more I play with it and the more I realize it has a fairly large overhead and foot print compared to WCF.

Re: HttpResponseMessage(HttpStatusCode.Conflict); returns a web page

aliostad

return new HttpResponseMessage<string>(null, HttpStatusCode.Conflict,
GlobalConfiguration.Configuration.Formatters.Where(x=>x.SupportedMediaTypes.Any(y=>y.MediaType == "application/json")));

Generic HttpRequestMessage and HttpResponseMessage are going away. See the latest bits: http://blogs.msdn.com/b/henrikn/archive/2012/04/29/using-nightly-nuget-packages-with-asp-net-web-stack.aspx

Re: HttpResponseMessage(HttpStatusCode.Conflict); returns a web page

Solved in VS 2012 RC. Great!