Continue
The server has received the request headers, and that the client should proceed to send the request body
http://tools.ietf.org/html/rfc7231#section-6.2.1The server has received the request headers, and that the client should proceed to send the request body
http://tools.ietf.org/html/rfc7231#section-6.2.1The requester has asked the server to switch protocols and the server is acknowledging that it will do so
http://tools.ietf.org/html/rfc7231#section-6.2.2Standard response for successful HTTP requests
http://tools.ietf.org/html/rfc7231#section-6.3.1The request has been fulfilled and resulted in a new resource being created
http://tools.ietf.org/html/rfc7231#section-6.3.2The request has been accepted for processing, but the processing has not been completed
http://tools.ietf.org/html/rfc7231#section-6.3.3The server successfully processed the request, but is returning information that may be from another source
http://tools.ietf.org/html/rfc7231#section-6.3.4The server successfully processed the request, but is not returning any content
http://tools.ietf.org/html/rfc7231#section-6.3.5The server successfully processed the request, but is not returning any content. Unlike a 204 response, this response requires that the requester reset the document view
http://tools.ietf.org/html/rfc7231#section-6.3.6The server is delivering only part of the resource (byte serving) due to a range header sent by the client
http://tools.ietf.org/html/rfc7233#section-4.1Indicates multiple options for the resource that the client may follow
http://tools.ietf.org/html/rfc7231#section-6.4.1This and all future requests should be directed to the given URI
http://tools.ietf.org/html/rfc7231#section-6.4.2The target resource resides temporarily under a different URI
http://tools.ietf.org/html/rfc7231#section-6.4.3The server is redirecting to a different URI which accesses the same resource
http://tools.ietf.org/html/rfc7231#section-6.4.4There is no need to retransmit the resource, since the client still has a previously-downloaded copy
http://tools.ietf.org/html/rfc7232#section-4.1The requested resource is only available through a proxy, whose address is provided in the response
http://tools.ietf.org/html/rfc7231#section-6.4.5Subsequent requests should use the specified proxy
http://tools.ietf.org/html/rfc7231#section-6.4.7The request could not be understood by the server due to malformed syntax
http://tools.ietf.org/html/rfc7231#section-6.5.1Authentication is required and has failed or has not yet been provided
http://tools.ietf.org/html/rfc7235#section-3.1The 402 (Payment Required) status code is reserved for future use
http://tools.ietf.org/html/rfc7231#section-6.5.2The server understood the request but refuses to authorize it
http://tools.ietf.org/html/rfc7231#section-6.5.3The requested resource could not be found but may be available again in the future
http://tools.ietf.org/html/rfc7231#section-6.5.4A request was made of a resource using a request method not supported by that resource
http://tools.ietf.org/html/rfc7231#section-6.5.5The requested resource is only capable of generating content not acceptable according to the Accept headers sent in the request
http://tools.ietf.org/html/rfc7231#section-6.5.6The client must first authenticate itself with the proxy
http://tools.ietf.org/html/rfc7235#section-3.2The server timed out waiting for the request
http://tools.ietf.org/html/rfc7231#section-6.5.7The request could not be processed because of conflict in the request
http://tools.ietf.org/html/rfc7231#section-6.5.8The resource requested is no longer available and will not be available again
http://tools.ietf.org/html/rfc7231#section-6.5.9The request did not specify the length of its content, which is required by the requested resource
http://tools.ietf.org/html/rfc7231#section-6.5.10The server does not meet one of the preconditions that the requester put on the request
http://tools.ietf.org/html/rfc7232#section-4.2The request is larger than the server is willing or able to process
http://tools.ietf.org/html/rfc7231#section-6.5.11The URI provided was too long for the server to process
http://tools.ietf.org/html/rfc7231#section-6.5.12The request entity has a media type which the server or resource does not support
http://tools.ietf.org/html/rfc7231#section-6.5.13The client has asked for a portion of the file (byte serving), but the server cannot supply that portion
http://tools.ietf.org/html/rfc7233#section-4.4The server cannot meet the requirements of the Expect request-header field
http://tools.ietf.org/html/rfc7231#section-6.5.14the server understands the content type of the request entity and the syntax of the request entity is correct but was unable to process the contained instructions.
https://tools.ietf.org/html/rfc4918#section-11.2The client should switch to a different protocol
http://tools.ietf.org/html/rfc7231#section-6.5.15The server encountered an unexpected condition that prevented it from fulfilling the request
http://tools.ietf.org/html/rfc7231#section-6.6.1The server does not support the functionality required to fulfill the request
http://tools.ietf.org/html/rfc7231#section-6.6.2The server, while acting as a gateway or proxy, received an invalid response from an inbound server
http://tools.ietf.org/html/rfc7231#section-6.6.3The server is currently unable to handle the request due to a temporary overload or scheduled maintenance
http://tools.ietf.org/html/rfc7231#section-6.6.4The server, while acting as a gateway or proxy, did not receive a timely response from an upstream server
http://tools.ietf.org/html/rfc7231#section-6.6.5The server does not support, or refuses to support, the major version of HTTP that was used in the request
http://tools.ietf.org/html/rfc7231#section-6.6.6