If something goes wrong in a WCF REST call, such as the requested resource is not found, how can I play with the HTTP response code (setting it to something like HTTP 404, for example) in my OperationContract method?
1
-
ok all the answers to this assume control made it into your service implementation. what if they pass some totally invalid uri? how are you suppose to provide a 404 for all the unexpected hits to your service?Nathan Tregillus– Nathan Tregillus2012-07-18 22:56:56 +00:00Commented Jul 18, 2012 at 22:56
Add a comment
|
7 Answers
There is a WebOperationContext that you can access and it has a OutgoingResponse property of type OutgoingWebResponseContext which has a StatusCode property that can be set.
WebOperationContext ctx = WebOperationContext.Current;
ctx.OutgoingResponse.StatusCode = System.Net.HttpStatusCode.OK;
answered Sep 26, 2008 at 15:16
Eric Schoonover
48.6k50 gold badges161 silver badges203 bronze badges
2 Comments
RyBolt
Does this work inside WCF Data Services - Service Operations ? I haven't had luck, seems the StatusCode I set gets trumped by something else. So on all HTTP POST requests, I get back 204 regardless that I set it at 201,etc.
Josh M.
Doesn't work in my case, the status gets overwritten. Throwing a
WebFaultException, however, does seem to work.If you need to return a reason body then have a look at WebFaultException
For example
throw new WebFaultException<string>("Bar wasn't Foo'd", HttpStatusCode.BadRequest );
4 Comments
Zephyr
I like this better than the accepted one since we are not using the static WebOperationContext.Current
sebagomez
keep in mind this is only valid since famework 4 msdn.microsoft.com/en-us/library/dd989924.aspx
Shavais
hmm, in .NET 4.5.1 this is not setting the status code for me, I'm still getting a 200. I'm using jsonp, it's calling my callback (in javascript) and passing my message and my status code as an integer.
crush
This seems great for anything outside of the 2XX codes, but would you throw a
WebFaultException to return an HttpStatusCode.Created?For 404 there is a built in method on the WebOperationContext.Current.OutgoingResponse called SetStatusAsNotFound(string message) that will set the status code to 404 and a status description with one call.
Note there is also, SetStatusAsCreated(Uri location) that will set the status code to 201 and location header with one call.
1 Comment
crush
Is this preferred over the method displayed in the accepted answer?
You can also return a statuscode and reason body with WebOperationContext's StatusCode and StatusDescription:
WebOperationContext context = WebOperationContext.Current;
context.OutgoingResponse.StatusCode = HttpStatusCode.OK;
context.OutgoingResponse.StatusDescription = "Your Message";
Comments
If you wish to see the status description in the header, REST method should make sure to return null from the Catch() section as below:
catch (ArgumentException ex)
{
WebOperationContext.Current.OutgoingResponse.StatusCode = HttpStatusCode.InternalServerError;
WebOperationContext.Current.OutgoingResponse.StatusDescription = ex.Message;
return null;
}
1 Comment
Shavais
This didn't work for me either, I still get a 200. I'm using WebHttpBinding with crossDomainScriptAccessEnabled="true" and an end point behaviour of webHttp with a default body style of wrapped and a default outgoing response format of json.. but that shouldn't matter, should it?
WebOperationContext.Current.OutgoingResponse.StatusCode = HttpStatusCode.Unauthorized;
throw new WebException("令牌码不正确", new InvalidTokenException());
Comments
This did not work for me for WCF Data Services. Instead, you can use DataServiceException in case of Data Services. Found the following post useful. http://social.msdn.microsoft.com/Forums/en/adodotnetdataservices/thread/f0cbab98-fcd7-4248-af81-5f74b019d8de
1 Comment
Shavais
That doesn't work for me either, I just get a 400 Bad Request, with no other useful information, and no response body.