200:HTTP_OK The request has succeeded.

201:HTTP_CREATED The request has been fulfilled and resulted in a new resource being created.

202:HTTP_ACCEPTED The request has been accepted for processing, but the processing has not been completed.

203:HTTP_NOT_AUTHORITATIVE The returned meta-information in the entity-header is not the definitive set as available from the origin server.

204:HTTP_NO_CONTENT The server has fulfilled the request but does not need to return an entity-body, and might want to return updated meta-information.

205:HTTP_RESET The server has fulfilled the request and the user agent SHOULD reset the document view which caused the request to be sent.

206:HTTP_PARTIAL The server has fulfilled the partial GET request for the resource.

300:HTTP_MULT_CHOICE 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.

301:HTTP_MOVED_PERM The requested resource has been assigned a new permanent URI and any future references to this resource SHOULD use one of the returned URIs.

302:HTTP_MOVED_TEMP The requested resource resides temporarily under a different URI.

303:HTTP_SEE_OTHER The response to the request can be found under a different URI and SHOULD be retrieved using a GET method on that resource.

304:HTTP_NOT_MODIFIED 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.

305:HTTP_USE_PROXY The requested resource MUST be accessed through the proxy given by the Location field.

307:HTTP_TEMP_REDIRECT The requested resource resides temporarily under a different URI.

400:HTTP_BAD_REQUEST The request could not be understood by the server due to malformed syntax.

401:HTTP_UNAUTHORIZED The request requires user authentication.

402:HTTP_PAYMENT_REQUIRED This code is reserved for future use.

403:HTTP_FORBIDDEN The server understood the request, but is refusing to fulfill it.

404:HTTP_NOT_FOUND The server has not found anything matching the Request-URI.

405:HTTP_BAD_METHOD The method specified in the Request-Line is not allowed for the resource identified by the Request-URI.

406:HTTP_NOT_ACCEPTABLE 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.

407:HTTP_PROXY_AUTH This code is similar to 401 (Unauthorized), but indicates that the client must first authenticate itself with the proxy.

408:HTTP_CLIENT_TIMEOUT The client did not produce a request within the time that the server was prepared to wait.

409:HTTP_CONFLICT The request could not be completed due to a conflict with the current state of the resource.

410:HTTP_GONE The requested resource is no longer available at the server and no forwarding address is known.

411:HTTP_LENGTH_REQUIRED The server refuses to accept the request without a defined Content- Length.

412:HTTP_PRECON_FAILED The precondition given in one or more of the request-header fields evaluated to false when it was tested on the server.

413:HTTP_ENTITY_TOO_LARGE The server is refusing to process a request because the request entity is larger than the server is willing or able to process.

414:HTTP_REQ_TOO_LONG The server is refusing to service the request because the Request-URI is longer than the server is willing to interpret.

415:HTTP_UNSUPPORTED_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.

416:HTTP_UNSUPPORTED_RANGE 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.

417:HTTP_EXPECT_FAILED 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.

500:HTTP_INTERNAL_ERROR The server encountered an unexpected condition which prevented it from fulfilling the request.

501:HTTP_NOT_IMPLEMENTED The server does not support the functionality required to fulfill the request.

502:HTTP_BAD_GATEWAY 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.

503:HTTP_UNAVAILABLE The server is currently unable to handle the request due to a temporary overloading or maintenance of the server.

504:HTTP_GATEWAY_TIMEOUT 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.

505:HTTP_VERSION The server does not support, or refuses to support, the HTTP protocol version that was used in the request message.