Request was received and processing can continue.
Request to switch protocols accepted.
Request completed successfully.
Request fulfilled and resulted in new resource being created.
Request accepted, but processing has not completed.
Information in Header is not from original server.
Request received; no information exists.
Request fulfilled; reset document view.
The server has fulfilled the partial GET request for the resource.
Requested address refers to more than one entity.
Page has been moved permanently; new URL available.
Page has been moved temporarily; new URL available.
Requested data is somewhere else; GET method should be used to retrieve it.
Requested resource has not been modified.
Requested resource must be accessed through proxy given by Location field.
Requested data temporarily resides at a new location.
Request could not be processed due to syntax error.
Client request did not include proper authentication data.
Payment is required. (Not implemented at this time. Reserved for future use.)
Request was understood, however access is forbidden.
Requested document could not be found.
The method being used to access the file is not allowed.
Request document does not exist in a format the client can accept.
Client must first authenticate with proxy for access.
The client did not produce a request within the time that the server was prepared to wait.
Request could not be completed due to a conflict with the resource.
Requested resource no longer exists and no forwarding address is known.
Request is missing required Content-Length header.
Request failed due to precondition not being met.
Request was too big to process.
Request refused due to URL being longer than server is willing to process.
Requested resource format is not supported.
Request includes a Range header and none of the ranges specified are contained within the requested resource.
The server is unable to meet the demands of the Expect header given by the client.
The server encountered an unexpected condition which prevented it from fulfilling the request.
The server does not support the functionality required to fulfill the request.
The server, while acting as a gateway or proxy, received an invalid response from an upstream provider.
The server is currently unable to handle the request due to a temporary overloading or maintenance of the server.
The server, while acting as a gateway or proxy, did not receive a timely response from an upstream provider.
The server does not support, or refuses to support, the HTTP protocol version that was used in the request.