I think you’re confusing two different semantic responses – one is telling the client that you successfully created a resource, and where it is. Whether the client goes to fetch it or not is a different story. The second is telling the client that it has sent the wrong location URI for a resource it’s … Read more
You can use HttpResponse class and using that you can access the status code as follows; HttpResponse httpResponse = client.newCall(request).execute(); httpResponse.getStatusLine().getStatusCode(); If you are using com.squareup.okhttp.Response then you can use the code() method to get the HTTP status code. Response httpResponse = client.newCall(request).execute(); httpResponse.code();
In my case it was not a firewall issue causing the StatusCode of 0. We were using a legacy app that was still using TLS 1.0 on a server that had blocked TLS 1.0 connections. Once we enabled TLS 1.2, we got the status codes we were expecting. System.Net.ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12;
Definitely do not abuse existing HTTP headers for this. Since it’s your own server, you get to define what the response looks like. You can (and should) pick whatever response works best for the intended recipient of this information and return the actual information in the response body. For example, if you are only interested … Read more
RESTful use of HTTP means that you must keep the API uniform. This means that you cannot add domain specific methods (ala GET_STOCK_QUOTE) but it also means that you cannot add domain specific error codes (ala 499 Product Out Of Stock). In fact, the HTTP client error codes are a good design check because if … Read more
As i’m reading it, 415 Unsupported Media Type sounds like the most appropriate. From RFC 2616: 10.4.16 415 Unsupported Media Type The server is refusing to service the request because the entity of the request is in a format not supported by the requested resource for the requested method. Yeah, the text part says “media … Read more
The exact satisfying one-time-for-all answer I found is: Short answer: 401 Unauthorized Description: While we know first is authentication (has the user logged-in or not?) and then we will go into authorization (does he have the needed privilege or not?), but here’s the key that makes us mistake: But isn’t “401 Unauthorized” about authorization, not … Read more
What about this one ? When requesting the login form which is a public page, you get what you want, so it’s a 200 status code : GET /login -> 200 When requesting for a page that needs a http level authentication that you didn’t initiated (basic http, ssl certificate, etc.), the application must tell … Read more