Another case: It could be possible to get a status code of 0 if you have sent an AJAX call and a refresh of the browser was triggered before getting the AJAX response. The AJAX call will be cancelled and you will get this status.
If you are strictly using the HTTP authentication framework provided by RFC 7235 for your REST API, the correct HTTP code would actually be 401. From the RFC: The 401 (Unauthorized) status code indicates that the request has not been applied because it lacks valid authentication credentials for the target resource. The server generating a … Read more
HttpURLConnection: URL url = new URL(“http://example.com”); HttpURLConnection connection = (HttpURLConnection)url.openConnection(); connection.setRequestMethod(“GET”); connection.connect(); int code = connection.getResponseCode(); This is by no means a robust example; you’ll need to handle IOExceptions and whatnot. But it should get you started. If you need something with more capability, check out HttpClient.
301: Permanent redirect. Clients making subsequent requests for this resource should use the new URI. Clients should not follow the redirect automatically for POST/PUT/DELETE requests. 302: Redirect for undefined reason. Clients making subsequent requests for this resource should not use the new URI. Clients should not follow the redirect automatically for POST/PUT/DELETE requests. 303: Redirect … Read more
I’d say 303 see other 302 Found: The requested resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client SHOULD continue to use the Request-URI for future requests. This response is only cacheable if indicated by a Cache-Control or Expires header field. fits a login page most closely … Read more
Getting overly clever with obscure-er HTTP error codes is a bad idea. Browsers sometimes react in unhelpful ways that obfuscate the situation. Stick with 404.
Maybe something like this… try { // … } catch (WebException ex) { if (ex.Status == WebExceptionStatus.ProtocolError) { var response = ex.Response as HttpWebResponse; if (response != null) { Console.WriteLine(“HTTP Status Code: ” + (int)response.StatusCode); } else { // no http status code available } } else { // no http status code available } … Read more
The idea is that the response body gives you a page that links you to the thing: 201 Created The 201 (Created) status code indicates that the request has been fulfilled and has resulted in one or more new resources being created. The primary resource created by the request is identified by either a Location … Read more
The approach I have taken is to just throw exceptions from the api controller actions and have an exception filter registered that processes the exception and sets an appropriate response on the action execution context. The filter exposes a fluent interface that provides a means of registering handlers for specific types of exceptions prior to … Read more
The “problem”, such as it is, is on the server side: the client has made a well formed request, but the server can not satisfy it. So I’m inclined to a “Server Error”, 5xx status code. Quoth RFC 7231 (the current HTTP standard, emphasis added): The 5xx (Server Error) class of status code indicates that … Read more