201 Created The request has been fulfilled, resulting in the creation of a new resource. In a POST request, the response will contain an entity describing or containing the result of the action. In a GET request, the response will contain an entity corresponding to the requested resource. The actual response will depend on the request method used. 200 OK Standard response for successful HTTP requests. This class of status codes indicates the action requested by the client was received, understood, accepted, and processed successfully. This code indicates that the server has received and is processing the request, but no response is available yet. This prevents the client from timing out and assuming the request was lost. 102 Processing (WebDAV RFC 2518) A WebDAV request may contain many sub-requests involving file operations, requiring a long time to complete the request. 101 Switching Protocols The requester has asked the server to switch protocols and the server has agreed to do so. The response 417 Expectation Failed indicates the request should not be continued. To have a server check the request's headers, a client must send Expect: 100-continue as a header in its initial request and receive a 100 Continue status code in response before sending the body. Sending a large request body to a server after a request has been rejected for inappropriate headers would be inefficient. 100 Continue The server has received the request headers and the client should proceed to send the request body (in the case of a request for which a body needs to be sent for example, a POST request). Since HTTP/1.0 did not define any 1xx status codes, servers must not send a 1xx response to an HTTP/1.0 client except under experimental conditions. This class of status code indicates a provisional response, consisting only of the Status-Line and optional headers, and is terminated by an empty line. Microsoft IIS sometimes uses additional decimal sub-codes to provide more specific information, but not all of those are here (note that these sub-codes only appear in the response payload and in documentation not in the place of an actual HTTP status code). The Internet Assigned Numbers Authority (IANA) maintains the official registry of HTTP status codes. Unless otherwise stated, the status code is part of the HTTP/1.1 standard. The phrases used are the standard wordings, but any human-readable alternative can be provided. The first digit of the status code specifies one of five classes of response an HTTP client must recognise these five classes at a minimum. It includes codes from IETF internet standards, other IETF RFCs, other specifications, and some additional commonly used codes. This is a list of Hypertext Transfer Protocol (HTTP) response status codes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |