广州凡科互联网科技有限公司

营业时间
MON-SAT 9:00-18:00

全国服务热线
18720358503

公司门店地址
广州市海珠区工业大道北67号凤凰创意园

http情况码中英文全解表

日期:2021-02-18 浏览:

http情况码中英文全解表


短视頻,自新闻媒体,达人种草1站服务

当访问者浏览1个网页页面时,访问者的访问器会向网页页面所属服务器传出恳求。当访问器接受并显示信息网页页面前,此网页页面所属的服务器会回到1个包括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情况码:

200 - 恳求取得成功

301 - 資源(网页页面等)被永久性迁移到其它URL

404 - 恳求的資源(网页页面等)不存在

500 - 內部服务器不正确

英文版

mon HTTP status code:

200 - The request was suessful

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

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

500 - Internal server error

情况码的归类

情况码由3个10进制数据构成,第1个10进制数据界定了情况码的种类,后两个数据沒有归类的功效。HTTP情况码共分成5类型型:归类叙述

1**:信息内容,服务器收到恳求,必须恳求者再次实行实际操作

2**:取得成功,实际操作被取得成功接受并解决

3**:重定项,必须进1步的实际操作以进行恳求

4**:顾客端不正确,恳求包括英语的语法不正确或没法进行恳求

5**:服务器不正确,服务器在解决恳求的全过程中产生了不正确

英文版

status code classification

The 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 suess, the operation was suessfully received and processed

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

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

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

HTTP情况码表

100:再次。顾客端应再次其恳求

101:切换协议书。服务器依据顾客端恳求切换协议书。只能切换到更高級的协议书,比如,切换到HTTP的新版本号协议书

2开始的情况码

200:恳求取得成功。1般用于GET与POST恳求

201:已建立。取得成功恳求并建立了新的資源

202:已接纳。早已接纳恳求,但未解决进行

203:非受权信息内容。恳求取得成功。但回到的meta信息内容不在初始的服务器,而是1个副本

204:无內容。服务器取得成功解决,但未回到內容。在未升级网页页面的状况下,可保证访问器再次显示信息当今文本文档

205:重设內容。服务器解决取得成功,客户终端设备(比如:访问器)应重设文本文档主视图。可根据此回到码消除访问器的表单域

206:一部分內容。服务器取得成功解决了一部分GET恳求

3开始的情况码

300:多种多样挑选。恳求的資源可包含好几个部位,相应可回到1个資源特点与详细地址的目录用于客户终端设备(比如:访问器)挑选

301:永久性挪动。恳求的資源已被永久性的挪动到新URI,回到信息内容会包含新的URI,访问器会全自动定项到新URI。将来任何新的恳求都应应用新的URI替代

302:临时性挪动。与301相近。但資源只是临时性被挪动。顾客端应再次应用原来URI

303:查询其它详细地址。与301相近。应用GET和POST恳求查询

304:未改动。所恳求的資源未改动,服务器回到此情况码时,不容易回到任何資源。顾客端一般会缓存文件浏览过的資源,根据出示1个头信息内容指出顾客端期待只回到在特定时间以后改动的資源

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:因为恳求的实体线过大,服务器没法解决,因而回绝恳求。为避免顾客端持续恳求,服务器将会会关掉联接。假如只是服务器临时没法解决,则会包括1个Retry-After的回应信息内容

414:恳求的URI太长(URI一般为网站地址),服务器没法解决

415:服务器没法解决恳求附带的新闻媒体文件格式

416:顾客端恳求的范畴失效

417:服务器没法考虑Expect的恳求头信息内容

5开始的情况码

500;服务器內部不正确,没法进行恳求

501:服务器不适用恳求的作用,没法进行恳求

502:当做网关或代理商的服务器,从远端服务器接受到了1个失效的恳求

503:因为超载或系统软件维护保养,服务器临时的没法解决顾客端恳求。延时的长度可包括在服务器的Retry-After头信息内容中

504:当做网关或代理商的服务器,未立即从远端服务器获得恳求

505:务器不适用恳求的HTTP协议书的版本号,没法进行解决

506:由《全透明內容商议协议书》(RFC 2295)拓展,意味着服务器存在內部配备不正确:被恳求的商议变元資源被配备为在全透明內容商议中应用自身,因而在1个商议解决中并不是1个适合的关键。

507:服务器没法储存进行恳求所务必的內容。这个情况被觉得是临时性的。WebDAV (RFC 4918)

509:服务器做到带宽限定。这并不是1个官方的情况码,可是仍被普遍应用。

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 aording 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 suessful. Generally used for GET and POST requests

201: Created. Suessfully requested and created new resource

202: Aepted. Already aepted the request but did not process it

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

204: No content. The server processed suessfully 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 suessfully 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 suessfully 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 aordingly 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 aessed 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 aessed 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 plete 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 plete 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 plete the request

501: The server does not support the requested functionality and can not plete 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 plete 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 plete 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)

 

作者:



新闻资讯

联系方式丨CONTACT

  • 全国热线:18720358503
  • 传真热线:18720358503
  • Q Q咨询:2639601583
  • 企业邮箱:2639601583@qq.com

首页
电话
短信
联系