http状态码中英文详解

网站站长都避免不了接触各种http状态码。为了让大家更好的了解各种http状态码，本文详细讲解，希望对大家有所帮助。

1xx(临时响应)

指示临时响应的状态代码，要求请求者在继续之前执行操作。

00(继续)请求者应该继续发出请求。当服务器返回这个代码时，意味着服务器已经收到请求的第一部分，现在正在等待接收其余部分。

01(切换协议)请求者已经请求服务器切换协议，服务器已经确认，准备切换。

2xx(成功)

用于指示服务器已成功处理请求的状态代码。

00(成功)服务器已成功处理请求。通常，这意味着服务器提供了请求的网页。如果您的robots.txt文件显示为这种状态，则意味着搜索引擎蜘蛛已经成功检索到该文件。

201 (Created)请求成功，服务器创建了一个新的资源。

02(已接受)服务器已接受请求，但尚未处理它。

03(未授权信息)服务器已成功处理请求，但返回的信息可能来自其他来源。

04(无内容)服务器成功处理了请求，但没有返回任何内容。

05(重置内容)服务器成功处理了请求，但没有返回任何内容。与204响应不同，此响应要求请求者重置文档视图(例如，清除表单内容以输入新内容)。

06(部分内容)服务器成功处理了一些GET请求。

3xx(已重定向)

无法抓取的错误网址。

00(多选)服务器可以根据请求进行各种操作。服务器可以根据用户代理选择操作，或者提供操作列表供请求者选择。

31(永久移动)请求的网页已被永久移动到新位置。当服务器返回这个响应(作为对GET或HEAD请求的响应)时，它会自动将请求者转移到一个新的位置。您应该使用此代码通知搜索引擎蜘蛛。

网页或网站已被永久移动到新位置。

32(临时移动)服务器当前正在响应来自不同位置的网页的请求，但是请求者应该继续使用原始位置用于将来的请求。该代码类似于响应GET和HEAD请求的301代码，并且将自动

去一个不同的地方。但是，由于搜索引擎蜘蛛会继续搜索原始位置并对其进行索引，因此您不应该使用此代码来通知搜索引擎蜘蛛某个页面或网站已被移动。

33(查看其他位置)当请求者应该向不同的位置发出单独的GET请求来检索响应时，服务器将返回此代码。对于除HEAD请求之外的所有请求，服务器将自动转到其他位置。

34(未修改)自上次请求以来，所请求的网页未被修改。当服务器返回此响应时，将不会返回网页内容。

如果web页面在请求者的最后一次请求之后没有改变，那么您应该配置服务器返回这个响应(称为If-Modified-Since HTTP header)。因为服务器可以告诉搜索引擎网页自上次爬行以来没有改变，所以可以节省带宽和开销。

35(使用代理)请求者只能使用代理来访问所请求的网页。如果服务器返回这个响应，服务器还将指示请求者应该使用的代理。

07(临时重定向)服务器当前正在响应来自不同位置的网页的请求，但是请求者应该继续使用原始位置用于将来的请求。该代码类似于响应GET和HEAD请求的301代码，并将自动发送

要求调到不同的位置。但是，由于搜索引擎蜘蛛会继续搜索原始位置并对其进行索引，因此您不应该使用此代码来通知搜索引擎蜘蛛某个页面或网站已被移动。

4xx(请求错误)

这些状态代码表明请求可能出错，这使得服务器无法处理该请求。

00(错误的请求)服务器不理解请求的语法。

41(未授权)请求需要验证。登录后，服务器可能会将此响应返回给页面。

403(禁止)服务器拒绝了请求。如果当搜索引擎蜘蛛试图抓取您网站上的有效网页时显示此状态代码(您可以在Google网站管理员工具中的诊断下的网页抓取页面上看到此状态代码)，则可能是您的服务器或主机拒绝搜索引擎蜘蛛访问它。

44(未找到)服务器找不到请求的网页。例如，如果请求的是服务器上不存在的网页，那么服务器通常会返回这个代码。

如果你的网站上没有robots.txt文件，那么，这就是正确的状态。但是，如果您有一个robots.txt文件并发现此状态，那么这意味着您的robots.txt文件可能命名不正确或位于错误的位置。(该文件应位于顶级域名上，命名为robots.txt)。

如果您在搜索引擎蜘蛛试图抓取的URL上发现此状态(在“诊断”选项卡的HTTP错误页面上)，则意味着搜索引擎蜘蛛可能正在跟踪另一个网页中的无效链接(旧链接或输入错误的链接)。

05(方法禁用)禁用请求中指定的方法。

46(不接受)无法使用请求的内容特征来响应请求

的网页。
407（需要代理授权） 此状态代码与 401（未授权）类似，但却指定了请求者应当使用代理进行授权。如果服务器返回此响应，那么，服务器还会指明请求者应当使用的代理。
408（请求超时）  服务器等候请求时超时。
409（冲突）  服务器在完成请求时发生冲突。服务器必须包含有关响应中所发生的冲突的信息。服务器在响应与前一个请求相冲突的 PUT 请求时可能会返回此代码，同时会提供两个请求的差异列表。
410（已删除）  如果请求的资源已被永久删除，那么，服务器会返回此响应。该代码与 404（未找到）代码类似，但在资源以前有但现在已经不复存在的情况下，有时会替代 404代码出现。如果资源已被永久删除，那么，您应当使用 301 代码指定该资源的新位置。
411（需要有效长度） 服务器不会接受包含无效内容长度标头字段的请求。
412（未满足前提条件） 服务器未满足请求者在请求中设置的其中一个前提条件。
413（请求实体过大） 服务器无法处理请求，因为请求实体过大，已超出服务器的处理能力。
414（请求的 URI 过长） 请求的 URI（通常为网址）过长，服务器无法进行处理。
415（不支持的媒体类型） 请求的格式不受请求页面的支持。
416（请求范围不符合要求） 如果请求是针对网页的无效范围进行的，那么，服务器会返回此状态代码。
417（未满足期望值） 服务器未满足”期望”请求标头字段的要求。
5xx（服务器错误）
这些状态代码表示，服务器在尝试处理请求时发生内部错误。这些错误可能是服务器本身的错误，而不是请求出错。
500（服务器内部错误）  服务器遇到错误，无法完成请求。

501（尚未实施） 服务器不具备完成请求的功能。例如，当服务器无法识别请求方法时，服务器可能会返回此代码。
502（错误网关） 服务器作为网关或代理，从上游服务器收到了无效的响应。
503（服务不可用） 目前无法使用服务器（由于超载或进行停机维护）。通常，这只是一种暂时的状态。
504（网关超时）  服务器作为网关或代理，未及时从上游服务器接收请求。
505（HTTP 版本不受支持） 服务器不支持请求中所使用的 HTTP 协议版本。

Web site owners to avoid exposure to various HTTP status code, in order to let everyone on the HTTP status code is more understanding, this paper detailed explanation of the HTTP status code.
1XX ( temporary response )
Used to indicate temporary response and request the execution operation to continue the status code.
100 ( Continued ) the requester shall continue to request. The server returns this code means, the server has received a request to the first part, we are waiting to receive the remainder.
101 ( Protocol ) the requester has asked the server protocol server has been confirmed, and prepare to switch.
2XX ( success)
Used to express server successfully processed the request status code.
200 ( success) server has been successfully processed the request. Usually, the said server provides the requested webpage. If your robots.txt file is displayed for this state, then, that the search engine spiders have been successfully retrieved the document.
201 ( created ) the request was successful and the server has created new resources.
202 ( accepted) server has accepted the request, but not for its treatment.
203 (unauthorized information ) server has been successfully processed the request, but returned may come from another source of information.
204 ( no content ) server successfully processed the request, but did not return any content.
205 ( reset content ) server successfully processed the request, but did not return any content. With 204 different response in response to the request, the request to reset the document view (such as removing the content of the form to enter new content ).
( Part 206 ) server successfully dealt with a portion of the GET request.
3xx ( redirected )
To mistake to crawl url.
300 ( multiple choice ) by the server can perform multiple operations. Server according to the requester ( User agent ) to select an operation, or operation list for a requester selects.
301 ( moved permanently ) request webpage has been permanently moved to a new location. The server returns the response ( as on GET or HEAD request response ), and will request to a new location. You should use this code notification of a search engine spider
A webpage or website has been permanently moved to a new location.
302 ( Temporary Mobile ) server is different from the position of the webpage in response to the request, the request should continue to use the original location for future requests. This code and the response of GET and HEAD request to the 301 code is similar, and will request
People go to a different location. But as a result of the search engine spiders will continue to capture the original position and the indexed, so you should not use this code to tell the search engine spiders a page or site has been moved.
303 ( see other position ) when the request to a different position was a separate GET request to retrieve a response, the server will return this code. In addition to the HEAD request for all but the request, the server automatically transferred to other locations.
304 ( unmodified) since the last request, request webpage has not been modified. The server returns the response, not return webpage content.
If the requester webpage since last request and never changed, you should configure the server to return the response ( known as If-Modified-Since HTTP header ). Because the server can tell the search engine spiders crawl after have changed since the last webpage, thus can save bandwidth and cost
305 ( proxy ) the requester can only use the proxy access request webpage. If the server returns the response, then the server will indicate the request, should use the proxy.
307 ( temporary redirect ) server is different from the position of the webpage in response to the request, the request should continue to use the original location for future requests. This code and the response of GET and HEAD request to the 301 code is similar, will automatically be please
Ask the person to a different location. But as a result of the search engine spiders will continue to capture the original position and the indexed, so you should not use this code to tell the search engine spiders a page or site has been moved.
4xx ( request error )
The status code indicates, the request may go wrong, has been hampered by the server to request processing.
400 ( error request server does not understand the grammar request ).
401 ( unauthorized ) request for authentication. After login, the server may return to the page of this response.
403 ( banned ) server refused request. If the search engine spider trying to crawl your site effective webpage show this status code ( you can be in the Google webmaster tools in the diagnosis of Web crawl page to see the status code ), then, this may be your server or host refused to search engine spiders of their visit.
404 ( not found) server could not find the requested webpage. For example, if the request is directed to the server doesn’t exist on the webpage of the, then, the server will typically return this code.
If you are not on site robots.txt files, so, this is the correct state. However, if you have a robots.txt file and found this state, so, this shows your robots.txt files may be naming errors or is in the wrong position. ( the file should be located in the top-level domain name, and shall be called robots.txt ).
If you are in a search engine spider trying to grab the website, discover this state (in the” diagnosis” label HTTP error page ), then, this means a search engine spider by tracking may be another webpage of invalid link ( old links or input error link).
405 ( method to disable disable ) specified in the request method.
406 ( not acceptable) cannot use the requested content characteristics in response to a request of the webpage.
407 ( need authorized agent ) this status code and 401 ( unauthorized ) is similar, but specifies a request should use the proxy authorization. If the server returns the response, then the server will indicate the request, should use the proxy.
408 ( request timeout ) server request timeout waiting for.
409 ( conflict ) server completes the request conflicts. The server must contain information about the response of the conflict between information. The server in response and a previous request conflicts with the PUT request may return this code, at the same time provide a two request to the difference list.
410 ( deleted ) if the requested resource has been permanently removed, then, the server will return the response. The code and 404 ( not found) code is similar, but the resources used to have but now no longer exists, sometimes replaced the 404 code appears. If the resource has been permanently removed, then, you should use a 301 code specifies that the resources of the new position.
411 (the need for effective length ) the server will not accept contains invalid Content-Length header field request.
412 (not to meet the prerequisite ) server does not satisfy the request in the request is set in one of the preconditions.
413 ( request entity too large ) server cannot process the request, because the request entity too large, has exceeded the processing power of the server.
414 ( URI request request too long ) URI ( usually for the URL ) is too long, the server can not be processed.
415 ( unsupported media type ) request format from the requested page support.
416 ( request scope does not meet the requirements of ) if the request is directed to webpage invalid was, then, the server will return the status code.
417 ( unmet expectations) server does not meet the” expectations” request-header field requirements.
5xx ( error )
The status code indicates, in attempt to handle the request server internal error. These errors may be the server itself is wrong, not request error.
500 ( internal server error the server encountered an error ), was unable to complete your request.
501 ( not implemented ) the server does not have to complete the requested function. For example, when the server is unable to identify the request method, the server may return this code.
502 ( error gateway ) server as a gateway or proxy, upstream from the server received an invalid response.
503 ( service not available ) is currently unavailable the server ( due to overloading or downtime for maintenance ). Usually, this is a temporary state.
504 ( Gateway timeout ) server as a gateway or proxy, not timely from the upstream server receives the request.
505 ( HTTP version is not supported ) the server does not support the request by the use of the HTTP protocol version.