http情况码英中文全解表

阅读  ·  发布日期 2021-03-29 07:57  ·  admin

http情况码英中文全解表


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

情况码的归类

情况码由三个十进制数据构成,第一个十进制数据界定了情况码的种类,后2个数据沒有归类的功效。HTTP情况码共有为5类型型:归类叙述

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

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

3**:跳转,必须进一步的实际操作以进行恳求

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:恳求取得成功。一般用以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:当做网关ip或代理商的网络服务器,从远端网络服务器接受来到一个失效的恳求

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

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

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 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)

 

创作者: haotuiwang/ 平头哥SEO,原創不容易,转截时务必以连接方式标明创作者和初始出處及本申明。


前不久一名网民在家里网上时,iPhoneSafari网页页面里常常弹出来“手中机淘宝网中开启连接吗?”的提醒框做为一位iOS码农,他很当然的了解它是网页页面在启用淘宝网app的URL


前不久,网站HTTPS处理计划方案出示商安信资格证书发布了本人编码签字资格证书,根据来资询有关资格证书的本人开发设计者客户量增加,安信特意选择了一款适合的Comodo本人编码签字资格证书。


Firefox的将来版本号将会会引进HTTPS-only方式,换句话说全方位阻拦浏览躁动不安全的网站。在全新发布的Firefox76Nightly版本号中,Mozilla引进了一项试验男性性功能,假如一切圆满可能在将来好多个月登录平稳版中,向全部客户对外开放。


无庸质疑,给手机软件安裝编码签字资格证书能够确保应用者的安全性。编码签字资格证书是数据资格证书的一种,是出示给测算机手机软件开发设计者应用的,两开发的手机软件编码开展数据签字。


前不久,很多iPhone客户体现见到系统软件持续地弹出窗口没法认证网络服务器真实身份,包含iOS、iPadOS及其macOS系统软件所有这般。在弹出窗口中iPhone标明不可以认证其真实身份,简易来讲便是这一网站域名的HTTPS资格证书没法被信赖。对于不可以被信赖的缘故倒是是非非常简易:因为电子邮箱忘掉给网络服务器拆换新资格证书,造成原资格证书期满后没法开展认证。


SEO推广软文如何写它是许多人头数疼的难题,在之前,检索模块没有什么內容,因此倡导,內容为王,外部链接为帝。显而易见,那时候候随意一一篇文章,基本都可以以百度收录,但那时候这类状况类似保持了五年上下


现如今这一填满机遇的制造行业不能防止的迈向衰落。雪崩的情况下沒有一片小雪花是无辜的,某度狼吞虎咽不好看,从事者急于求成,这一制造行业早已青黄不接。在此纪录一下自身所掌握的SEO制造行业,见到的众生相。


外部链接说白了便是指自身网站的全部网站偏向本身的连接。是构成互连网的关键基本之一,外部链接是互连网的血夜,是联接的一种。沒有连接,信息内容是独立的,結果便是全都看不见。就例如一个网站的內容毫无疑问不容易全部的內容都承重在一个网页页面


昨日在家里确实无趣,开启电脑上进到访问器刚开始发愣,因为我头脑里是在想我可以学习培训甚么超级技能或是专业知识呢,我的手也不由独立的在检索框里键入了:学点啥呢。这一心理状态主题活动立即造成我还在检索模块键入了我还的真正念头,也就是我最近最有要求的事情,因此十今后进去就要来和大伙儿剖析一下,客户检索时在想甚么?


大家都知道SEM运营专员必需的一项专业技能便是数据信息剖析,仅有剖析帐户之后才可以清楚一目了然的了解帐户出現的难题,今日十今后就需要和大伙儿共享一下SEM竟价中的四象限剖析规律,期待能够给诸位SEMer剖析帐户产生一点构思和思绪。


继阿里巴巴,腾迅,京东商城,快手视频,抖音短视频都搞起来了直播间卖房子,涉足房地产业务流程后,百度搜索此次也没晚到,最近发布了自身的房地产买卖信息网站”百度搜索房地产“出示网上卖房子看楼服务。


大搜ocpc是一把双刃刀,用到好,实际效果十分好。用的不太好会导致非常大的消耗。即便大搜ocpc早已发布一年多了,一直至如今,也有许多人对它提出质疑,觉得没有什么实际效果或是其实不功能强大。那麼我觉得告知你,你确实不对。


在互联网营销推广风靡的时期,如今建立网站营销推广要重视的关键点能变得越来越越大,特别是在是百度搜索提升时,许多网站关键点都将决策网络推广实际效果的优劣。现如今许多公司网站都存有那样的一个常见问题


最近贵州省的一些中小型公司朋友私聊了我一个难题:自身干了一个提升型的网站,百度关键词有排行,网站有总流量,可是一直沒有外贸询盘留言板留言,更沒有电話资询,这类状况如何办呢?


近年来来企业网站建设较大的发展趋势是响应式网页页面设计方案已越来越越来越越时兴和关键。可是,响应式设计方案能够追朔到好长时间之前。具体上,第一个网站的合理布局能够适应不一样的访问器视口总宽,它是在二零零二年上下设计方案的。因为技术性的发展及其为互联网设计方案一直寓意着要设计方案成千上万显示屏规格的客观事实,自适应网站设计方案是当然的結果。