Java api http response
202: The request has been accepted for processing, but the processing has not been completed, see Hypertext Transfer Protocol — HTTP/1.1.
502: The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request, see Hypertext Transfer Protocol — HTTP/1.1.
400: The request could not be understood by the server due to malformed syntax, see Hypertext Transfer Protocol — HTTP/1.1.
409: The request could not be completed due to a conflict with the current state of the resource, see Hypertext Transfer Protocol — HTTP/1.1.
201: The request has been fulfilled and resulted in a new resource being created, see Hypertext Transfer Protocol — HTTP/1.1.
417: The expectation given in an Expect request-header field could not be met by this server, or, if the server is a proxy, the server has unambiguous evidence that the request could not be met by the next-hop server.
302: The requested resource resides temporarily under a different URI, see Hypertext Transfer Protocol — HTTP/1.1.
504: The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server specified by the URI or some other auxiliary server it needed to access in attempting to complete the request.
410: The requested resource is no longer available at the server and no forwarding address is known, see Hypertext Transfer Protocol — HTTP/1.1.
505: The server does not support, or refuses to support, the HTTP protocol version that was used in the request message.
500: The server encountered an unexpected condition which prevented it from fulfilling the request, see Hypertext Transfer Protocol — HTTP/1.1.
411: The server refuses to accept the request without a defined Content-Length, see Hypertext Transfer Protocol — HTTP/1.1.
405: The method specified in the Request-Line is not allowed for the resource identified by the Request-URI, see Hypertext Transfer Protocol — HTTP/1.1.
301: The requested resource has been assigned a new permanent URI and any future references to this resource SHOULD use one of the returned URIs, see Hypertext Transfer Protocol — HTTP/1.1.
300: The requested resource corresponds to any one of a set of representations, each with its own specific location, and agent- driven negotiation information is being provided so that the user (or user agent) can select a preferred representation and redirect its request to that location, see Hypertext Transfer Protocol — HTTP/1.1.
204: The server has fulfilled the request but does not need to return an entity-body, and might want to return updated meta-information, see Hypertext Transfer Protocol — HTTP/1.1.
203: The returned meta-information in the entity-header is not the definitive set as available from the origin server, see Hypertext Transfer Protocol — HTTP/1.1.
406: The resource identified by the request is only capable of generating response entities which have content characteristics not acceptable according to the accept headers sent in the request, see Hypertext Transfer Protocol — HTTP/1.1.
501: The server does not support the functionality required to fulfill the request, see Hypertext Transfer Protocol — HTTP/1.1.
304: If the client has performed a conditional GET request and access is allowed, but the document has not been modified, the server SHOULD respond with this status code, see Hypertext Transfer Protocol — HTTP/1.1.
206: The server has fulfilled the partial GET request for the resource, see Hypertext Transfer Protocol — HTTP/1.1.
412: The precondition given in one or more of the request-header fields evaluated to false when it was tested on the server, see Hypertext Transfer Protocol — HTTP/1.1.
407: This code is similar to 401 (Unauthorized), but indicates that the client must first authenticate itself with the proxy, see Hypertext Transfer Protocol — HTTP/1.1.
413: The server is refusing to process a request because the request entity is larger than the server is willing or able to process, see Hypertext Transfer Protocol — HTTP/1.1.
414: The server is refusing to service the request because the Request-URI is longer than the server is willing to interpret, see Hypertext Transfer Protocol — HTTP/1.1.
416: A server SHOULD return a response with this status code if a request included a Range request-header field , and none of the range-specifier values in this field overlap the current extent of the selected resource, and the request did not include an If-Range request-header field.
205: The server has fulfilled the request and the user agent SHOULD reset the document view which caused the request to be sent, see Hypertext Transfer Protocol — HTTP/1.1.
303: The response to the request can be found under a different URI and SHOULD be retrieved using a GET method on that resource, see Hypertext Transfer Protocol — HTTP/1.1.
503: The server is currently unable to handle the request due to a temporary overloading or maintenance of the server, see Hypertext Transfer Protocol — HTTP/1.1.
307: The requested resource resides temporarily under a different URI, see Hypertext Transfer Protocol — HTTP/1.1.
415: 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, see Hypertext Transfer Protocol — HTTP/1.1.
305: The requested resource MUST be accessed through the proxy given by the Location field, see Hypertext Transfer Protocol — HTTP/1.1.