当欣赏者访问一个网页时，欣赏者的欣赏器会向网页地点办事器发出哀求。当欣赏器吸收并表现网页前，此网页地点的办事器会返回一个包罗HTTP状态码的信息头（server header）用以相应欣赏器的哀求。

英文版

When a visitor visits a webpage, the browser of the visitor makes a request to the server where the webpage is located. When the browser receives and displays the web page, the server on which the web page resides returns a server header containing the HTTP status code to respond to the browser's request.

http常见的HTTP状态码：

200 - 哀求乐成

301 - 资源（网页等）被永世转移到别的URL

404 - 哀求的资源（网页等）不存在

500 - 内部办事器错误

英文版

http common HTTP status code:

200 - The request was successful

301 - Resources (web pages, etc.) are permanently transferred to other URLs

404 - The requested resource (webpage, etc.) does not exist

500 - Internal server error

http状态码的分类

http状态码由三个十进制数字构成，第一个十进制数字界说了状态码的范例，后两个数字没有分类的作用。HTTP状态码共分为5种范例：分类形貌

1**：信息，办事器收到哀求，必要哀求者继承实行操纵

2**：乐成，操纵被乐成吸收并处置惩罚

3**：重定向，必要进一步的操纵以完成哀求

4**：客户端错误，哀求包罗语法错误或无法完成哀求

5**：办事器错误，办事器在处置惩罚哀求的历程中产生了错误

英文版

http status code classification

The http status code consists of three decimal digits. The first decimal digit defines the type of status code. The last two digits have no classification. HTTP status code is divided into 5 types: classification description

1 **: information, the server receives the request, the requester need to continue to operate

2 **: On success, the operation was successfully received and processed

3 **: Redirect, requires further action to complete the request

4 **: client error, request contains a syntax error or can not complete the request

5 **: server error, the server has encountered an error while processing the request

HTTP状态码表

100：继承。客户端应继承其哀求

101：切换协议。办事器凭据客户端的哀求切换协议。只能切换到更高级的协议，比方，切换到HTTP的新版本协议

2开头的状态码

200：哀求乐成。一样平常用于GET与POST哀求

201：已创建。乐成哀求并创建了新的资源

202：已担当。已经担当哀求，但未处置惩罚完成

203：非授权信息。哀求乐成。但返回的meta信息不在原始的办事器，而是一个副本

204：无内容。办事器乐成处置惩罚，但未返回内容。在未更新网页的环境下，可确保欣赏器继承表现当前文档

205：重置内容。办事器处置惩罚乐成，用户终端（比方：欣赏器）应重置文档视图。可通过此返回码扫除欣赏器的表单域

206：部门内容。办事器乐成处置惩罚了部门GET哀求

3开头的状态码

300：多种选择。哀求的资源可包罗多个位置，相应可返回一个资源特性与地点的列表用于用户终端（比方：欣赏器）选择

301：永世移动。哀求的资源已被永世的移动到新URI，返复书息会包罗新的URI，欣赏器会主动定向到新URI。以后任何新的哀求都应利用新的URI取代

302：暂时移动。与301雷同。但资源只是暂时被移动。客户端应继承利用原有URI

303：检察别的地点。与301雷同。利用GET和POST哀求检察

304：未修改。所哀求的资源未修改，办事器返回此状态码时，不会返回任何资源。客户端通常会缓存访问过的资源，通过提供一个头信息指出客户端盼望只返回在指定日期之后修改的资源

305：利用署理。所哀求的资源必须通过署理访问

306：已经被废弃的HTTP状态码

307：暂时重定向。与302雷同。利用GET哀求重定向

4开头的状态码

400：客户端哀求的语法错误，办事器无法明白

401：哀求要求用户的身份认证

402：保存，未来利用

403：办事器明白哀求客户端的哀求，但是拒绝实行此哀求

404：办事器无法凭据客户端的哀求找到资源（网页）。通过此代码，网站计划职员可设置"您所哀求的资源无法找到"的本性页面

405：客户端哀求中的要领被克制

406：办事器无法凭据客户端哀求的内容特性完成哀求

407：哀求要求署理的身份认证，与401雷同，但哀求者应当利用署理举行授权

408：办事器等候客户端发送的哀求时间过长，超时

409：办事器完成客户端的PUT哀求是大概返回此代码，办事器处置惩罚哀求时产生了辩论

410：客户端哀求的资源已经不存在。410差别于404，假如资源从前有如今被永世删除了可利用410代码，网站计划职员可通过301代码指定资源的新位置

411：办事器无法处置惩罚客户端发送的不带Content-Length的哀求信息

412：客户端哀求信息的先决条件错误

413：由于哀求的实体过大，办事器无法处置惩罚，因此拒绝哀求。为防备客户端的一连哀求，办事器大概会封闭毗连。假如只是办事器临时无法处置惩罚，则会包罗一个Retry-After的相应信息

414：哀求的URI过长（URI通常为网址），办事器无法处置惩罚

415：办事器无法处置惩罚哀求附带的媒体格式

416：客户端哀求的范畴无效

417：办事器无法满意Expect的哀求头信息

5开头的状态码

500；办事器内部错误，无法完成哀求

501：办事器不支持哀求的功效，无法完成哀求

502：充当网关或署理的办事器，从远端办事器吸收到了一个无效的哀求

503：由于超载或体系维护，办事器临时的无法处置惩罚客户端的哀求。延时的长度可包罗在办事器的Retry-After头信息中

504：充当网关或署理的办事器，未实时从远端办事器获取哀求

505：务器不支持哀求的HTTP协议的版本，无法完成处置惩罚

506：由《透明内容协商协议》（RFC 2295）扩展，代表办事器存在内部设置错误：被哀求的协商变元资源被设置为在透明内容协商中利用本身，因此在一个协商处置惩罚中不是一个符合的重点。

507：办事器无法存储完成哀求所必须的内容。这个状态被以为是暂时的。WebDAV (RFC 4918)

509：办事器到达带脱期制。这不是一个官方的状态码，但是仍被遍及利用。

510：获取资源所必要的计谋并没有没满意。（RFC 2774）

英文版

HTTP Status Code Table (Version 1)

100: continue. Clients should continue their request

101: Switch the protocol. The server switches the protocol according to the client's request. You can only switch to more advanced protocols, for example, to switch to the new version of HTTP

2 The beginning of the status code

200: The request was successful. Generally used for GET and POST requests

201: Created. Successfully requested and created new resource

202: Accepted. Already accepted the request but did not process it

203: unauthorized information. The request is successful. But the meta-information returned is not a copy of the original server, but a copy

204: No content. The server processed successfully but did not return content. Without updating the page, make sure that the browser continues to display the current document

205: Reset content. If the server is successfully processed, the user terminal (for example, browser) should reset the document view. This return code can be used to clear the browser's form fields

206: part of the content. The server successfully processed part of the GET request

3 at the beginning of the status code

300: a variety of options. The requested resource can include multiple locations, and a list of resource features and addresses can be returned accordingly for the user terminal (eg, browser) to select

301: move permanently. The requested resource has been permanently moved to the new URI, the returned information will include the new URI, and the browser will automatically redirect to the new URI. Any new requests in the future should use the new URI instead

302: temporary move. Similar to 301. But resources are only temporarily moved. The client should continue to use the original URI

303: View other addresses. Similar to 301. View using GET and POST requests

304: unmodified. The requested resource is unmodified, and the server does not return any resources when it returns this status code. Clients typically cache accessed resources by providing a header that states that the client wants to return only those resources that were modified after the specified date

305: Use a proxy. The requested resource must be accessed through a proxy

306: HTTP status code that has been discarded

307: temporary redirect. Similar to 302. Use GET request redirection

4 The beginning of the status code

400: Client request syntax error, the server can not understand

401: The request asks the user for authentication

402: Reserved for future use

403: The server understands the request for the client, but refuses to execute the request

404: The server could not find the resource (web page) based on the client's request. With this code, a website designer can set a personalized page that says "The resource you requested can not be found."

405: The method in the client request is disabled

406: The server can not complete the request based on the content characteristics requested by the client

407: The request asks for the identity of the proxy, similar to 401, but the requester should use the proxy for authorization

408: The server waits for the client to send the request for too long, timeout

409: The server may complete the client's PUT request is likely to return this code, the server encountered a request conflict

410: The client requested resource no longer exists. 410 is different from 404, if the resource has been permanently deleted for the 410 code, the site designer can specify the new location of the resource with the 301 code

411: The server was unable to process the request message sent by the client without Content-Length

412: Client request information is a prerequisite error

413: The request is denied because the requested entity is too large for the server to process. To prevent continuous client requests, the server may close the connection. If only the server temporarily unable to deal with, it will contain a Retry-After response

414: Request URI is too long (URI is usually the URL), the server can not handle

415: The server was unable to process the media format attached to the request

416: Invalid client request range

417: The server can not satisfy Expect's request header information

5 The beginning of the status code

500; internal server error, unable to complete the request

501: The server does not support the requested functionality and can not complete the request

502: A server acting as a gateway or proxy receives an invalid request from a remote server

503: The server is temporarily unable to process the client's request due to overloading or system maintenance. The length of the delay can be included in the server's Retry-After header

504: act as a gateway or proxy server, did not get requests from the remote server in time

505: The server does not support the requested version of the HTTP protocol and can not complete the process

506: Expanded by Transparent Content Negotiation Protocol (RFC 2295), representing an internal configuration error on behalf of the server: The requested Negotiation Argument resource is configured to use itself in transparent content negotiation and is therefore not suitable in a negotiation process Focus.

507: The server can not store the content necessary to complete the request. This situation is considered temporary. WebDAV (RFC 4918)

509: The server reached the bandwidth limit. This is not an official status code, but is still widely used.

510: The strategy needed to get the resource is not missing. (RFC 2774)

作者: https://www.haotuiwang.cn/ 平头哥SEO，原创不易，转载时必须以链接情势注明作者和原始出处及本声明。