本文描述了常用的Http响应状态，后面用英文写，但我的英文不太好，如有错误之处，希望大家帮我纠正，我的联系方式在后面。
183Please respect copyright.ＰＥＮＡＮＡoiCvibb3On
Section A. Most Often Used
200 OK183Please respect copyright.ＰＥＮＡＮＡsFODWRs0UZ
The request succeeded.
206 Partial Content183Please respect copyright.ＰＥＮＡＮＡ2K50tzjRz5
This response code is used in response to a range request when the client has requested a part or parts of a resource.
304 Not Modified183Please respect copyright.ＰＥＮＡＮＡjnq8x9nLja
This is used for caching purposes. It tells the client that the response has not been modified, so the client can continue to use the same cached version of the response.
400 Bad Request183Please respect copyright.ＰＥＮＡＮＡrrNWvo32Wq
The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).
401 Unauthorized183Please respect copyright.ＰＥＮＡＮＡVjVJ4pJgV4
Although the HTTP standard specifies "unauthorized", semantically this response means "unauthenticated". That is, the client must authenticate itself to get the requested response.
403 Forbidden183Please respect copyright.ＰＥＮＡＮＡiyHVGj5HOR
The client does not have access rights to the content; that is, it is unauthorized, so the server is refusing to give the requested resource. Unlike 401 Unauthorized, the client's identity is known to the server.
404 Not Found183Please respect copyright.ＰＥＮＡＮＡ7VkHIyk3Do
The server cannot find the requested resource. In the browser, this means the URL is not recognized. In an API, this can also mean that the endpoint is valid but the resource itself does not exist. Servers may also send this response instead of 403 Forbidden to hide the existence of a resource from an unauthorized client. This response code is probably the most well known due to its frequent occurrence on the web.
411 Length Required183Please respect copyright.ＰＥＮＡＮＡRYUeOscyuT
Server rejected the request because the Content-Length header field is not defined and the server requires it.
413 Content Too Large183Please respect copyright.ＰＥＮＡＮＡoKB7XiTkaE
The request body is larger than limits defined by server. The server might close the connection or return an Retry-After header field.
414 URI Too Long183Please respect copyright.ＰＥＮＡＮＡHCb55d3bN7
The URI requested by the client is longer than the server is willing to interpret.
416 Range Not Satisfiable183Please respect copyright.ＰＥＮＡＮＡH28MtY0Kka
The ranges specified by the Range header field in the request cannot be fulfilled. It's possible that the range is outside the size of the target resource's data.
431 Request Header Fields Too Large183Please respect copyright.ＰＥＮＡＮＡdEzyYwvCYY
The server is unwilling to process the request because its header fields are too large. The request may be resubmitted after reducing the size of the request header fields.
500 Internal Server Error183Please respect copyright.ＰＥＮＡＮＡlvFrgzA5PU
The server has encountered a situation it does not know how to handle. This error is generic, indicating that the server cannot find a more appropriate 5XX status code to respond with.
505 HTTP Version Not Supported183Please respect copyright.ＰＥＮＡＮＡSWX75Exdhe
The HTTP version used in the request is not supported by the server.
Section B. Sometimes Used
101 Switching Protocols183Please respect copyright.ＰＥＮＡＮＡI2tThZcvzb
This code is sent in response to an Upgrade request header from the client and indicates the protocol the server is switching to.
301 Moved Permanently183Please respect copyright.ＰＥＮＡＮＡSsF2CzsJKO
The URL of the requested resource has been changed permanently. The new URL is given in the response.
308 Permanent Redirect183Please respect copyright.ＰＥＮＡＮＡK9nBbfouXU
This means that the resource is now permanently located at another URI, specified by the Location response header. This has the same semantics as the 301 Moved Permanently HTTP response code, with the exception that the user agent must not change the HTTP method used: if a POST was used in the first request, a POST must be used in the second request.
412 Precondition Failed183Please respect copyright.ＰＥＮＡＮＡk1Ze5xxgN2
In conditional requests, the client has indicated preconditions in its headers which the server does not meet.
417 Expectation Failed183Please respect copyright.ＰＥＮＡＮＡFRwBLXxL18
This response code means the expectation indicated by the Expect request header field cannot be met by the server.
426 Upgrade Required183Please respect copyright.ＰＥＮＡＮＡimHs7SAjNw
The server refuses to perform the request using the current protocol but might be willing to do so after the client upgrades to a different protocol. The server sends an Upgrade header in a 426 response to indicate the required protocol(s).
428 Precondition Required183Please respect copyright.ＰＥＮＡＮＡHunmIQtzXY
The origin server requires the request to be conditional. This response is intended to prevent the 'lost update' problem, where a client GETs a resource's state, modifies it and PUTs it back to the server, when meanwhile a third party has modified the state on the server, leading to a conflict.
503 Service Unavailable183Please respect copyright.ＰＥＮＡＮＡLhuWaYstpU
The server is not ready to handle the request. Common causes are a server that is down for maintenance or that is overloaded. Note that together with this response, a user-friendly page explaining the problem should be sent. This response should be used for temporary conditions and the Retry-After HTTP header should, if possible, contain the estimated time before the recovery of the service. The webmaster must also take care about the caching-related headers that are sent along with this response, as these temporary condition responses should usually not be cached.
Section C. Thanks
https://developer.mozilla.org/en-US/docs/Web/HTTP/Status
183Please respect copyright.ＰＥＮＡＮＡrPLstoizdS
Section D. Contacts Me
If you found any errors or have any suggestions for this article, please let me know, my wechat: si_jinmin, my email: [email protected]183Please respect copyright.ＰＥＮＡＮＡcVXaPBBTnC
如果您发现本文有任何错误，或者对本文有好的建议，欢迎与我联系探讨，我的微信: si_jinmin, 我的email: [email protected]
如果您對C/C++ programming, Linux, website development, Vue, Git, vscode感興趣，邀請您加入「Linux/C/C++ Website Development」 微信群，請加我的微信（si_jinmin）以便拉您进群。
ns216.73.216.238da2
