2024年1月16日发(作者：)

HTML错误代码（HTML error code）

http错误代码含义:

“100”:继续

“101”:有魅力的协议

“200”:好的

“201”:创建

“202”:接受

“203”:那些信息

“204”:没有内容

“205”:重置内容

“206”:部分内容

“300”:多个选择

“301”:永久移动

“302”:发现

“303”:看

“304”:不修改

“305”:使用代理

“307”:临时重定向

“400”:糟糕的请求

“401”:未经授权

“402”:要求付款

“403”:禁止的

“404”:未找到

“405”:不允许的方法

“406”:不能接受的

“407”:代理身份验证

“408”:请求暂停

“409”:冲突

“410”:走了

“411”:长度要求

“412”:失败的先决条件

“413”:请求实体太大

“414”:请求-uri太大

“415”:不支持的媒体类型

“416”:要求的范围不能满足

“417”:期望失败了

“500”:内部服务器错误

“501”:没有实现

“502”:糟糕的网关

“503”:服务不可用

“504”:网关超时

“505”:不支持HTTP版本

1 xx(临时响应)

表示临时响应并需要请求者继续执行操作的状态代码。

代码说明

100(继续)请求者应当继续提出请求。服务器返回此代码表示已收到请求的第一部分,正在等待其余部分。

101(切换协议)请求者已要求服务器切换协议,服务器已确认并准备

切换。

2 xx(成功)

表示成功处理了请求的状态代码。代码说明

200(成功)服务器已成功处理了请求。通常,这表示服务器提供了请求的网页。如果针对您的机器人。txt文件显示此状态代码,则表示广告已成功检索到该文件。

201(已创建)请求成功并且服务器创建了新的资源。

202(已接受)服务器已接受请求,但尚未处理。

203(非授权信息)服务器已成功处理了请求,但返回的信息可能来自另一来源。

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

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

206(部分内容)服务器成功处理了部分得到请求。

3 xx(重定向)

要完成请求,需要进一步操作。通常,

These state codes are used to redirect. Google suggests that

you use redirection less than five times per request. You can

use the webmaster tool to see if the Googlebot encounters

problems while fetching redirected pages. The web crawl page

of the diagnosis lists urls that Googlebot cannot crawl due to

redirection errors. Code instructions

300 (multiple choices) for the request, the server can perform

multiple operations. The server can select an operation based

on the user agent or provide a list of actions for the requestor

to select.

The page of the 301 (permanently moving) request has moved

permanently to the new location. When the server returns this

response (response to a GET or HEAD request), the requester is

automatically transferred to a new location. You should use

this code to tell Googlebot that a page or website has moved

permanently to a new location.

The 302 (temporary mobile) server currently responds to

requests from different locations, but the requester should

continue to use the original location for subsequent requests.

This code is similar to the 301 code response to a GET or HEAD

request, will automatically transfer the requestor to a

different position, but you should not use this code to tell

Googlebot a page or site has been moving, because Googlebot will

continue to grab the original position and indexing.

303 (view other location) the requester should use a separate

GET request for the different locations to retrieve the

response, which the server returns. For all requests except

HEAD, the server automatically moves to another location.

304 (unchanged) since the last request, the requested page has

not been modified. When the server returns this response, the

page content is not returned. If the web page has not changed

Since the last request, you should configure the server to

return this response (called If - modified-since HTTP header).

Since the server can tell Googlebot that the page has not

changed since the last scraping, it can save bandwidth and cost.

The 305 (using the proxy) requesters can only use the web page

that the agent accesses the request. If the server returns this

response, it also indicates that the requestor should use the

proxy.

The 307 (temporary redirect) server now responds to requests

from different locations, but the requester should continue to

use the original location to make subsequent requests. This

code is similar to the 301 code response the GET and HEAD

requests, will automatically transfer the requestor to a

different position, but you should not use this code to tell

Googlebot a page or site has been moving, because the Googlebot

will continue to grab the original position and indexing.

4xx (request error)

These state codes indicate that the request can go awry,

hindering the processing of the server. Code instructions

The server does not understand the syntax of the request.

401 (unauthorized) request for authentication. For web pages

that need to be logged in, the server may return this response.

The 403 (forbidden) server refused the request.

If you are Googlebot when trying to grab the effective web pages

on your web site to see the status code (can be in Google

webmaster tools under the diagnosis of web scraping of the page

to see this information), may be your server or host refuses

to Googlebot access.

404 (not found) server can not find the requested page. For

example, web pages that don't exist on a server often return

this code. If you don't have a file on your website,

and you see it on the page of the Google webmaster

tool "diagnostics" TAB, this is the correct state. However, if

you have a file and see this state, then your

file may be named wrong or in the wrong location (the

file should be in the top-level domain name, called ).

If for Googlebot trying to grab web site to see this state (in

the "diagnosis" tag HTTP error page), said Googlebot track may

be invalid link on another page (old links or enters the wrong

link).

405 (methods disable) to disable the method specified in the

request.

406 (unacceptable) you cannot use the requested content feature

to respond to the requested page.

407 (you need an agent authorization) this state code is similar

to the 401 (unauthorized), but the specified requestor should

authorize the use of the agent. If the server returns this

response, it also indicates the agent that the requester should

use.

A timeout occurs when the server waits for the request.

The 409 (conflict) server conflicts when the request is

completed. The server must contain information about the

conflict in the response. The server may return this code in

response to a PUT request that conflicts with the previous

request, along with a list of differences between the two

requests.

410 (deleted) if the requested resource has been permanently

deleted, the server will return this response. This code is

similar to a 404 (not found) code, but it is sometimes used as

an alternative to the 404 code before resources exist and are

not present. If the resource has been permanently deleted, you

should use a new location for the resource in 301.

411 (valid length) server does not accept requests without

valid content length header fields.

The server fails to meet one of the prerequisites set in the

request by the requestor.

413 (request entity oversize) server cannot handle requests

because the request entity is too large to handle the server's

processing power.

414 (the requested URI is too long) the requested URI (usually

the url) is too long for the server to handle.

The format requested by 415 (unsupported media types) is not

supported by the requested page.

416 (request scope does not meet the requirements) if the page

cannot provide the scope of the request, the server returns this

status code.

417 (unmet expectations) server does not meet the requirements

of "expectation" request header field.

5xx (server error)

These state codes indicate that an internal error occurred

while the server was trying to process the request. These errors

may be the error of the server itself, not the request for error.

Code instructions

500 (server internal error) server encountered an error and

unable to complete the request.

501 (unimplemented) server does not have the function to

complete the request. For example, the server might return this

code when it cannot identify the request method.

The 502 (error gateway) server receives an invalid response

from the upstream server as a gateway or proxy.

503 (service unavailable) servers are currently unavailable

(due to overloading or downtime maintenance). Usually, this is

temporary.

504 (gateway timeout) server as a gateway or proxy, but not in

time to receive requests from the upstream server.

The 505 (HTTP version unsupported) server does not support the

HTTP protocol version used in the request.