[{"data":1,"prerenderedAt":475},["ShallowReactive",2],{"doc-\u002Fdocs\u002Fhttp-status-codes":3,"docs-all":370},{"id":4,"title":5,"body":6,"category":354,"date":355,"description":356,"draft":357,"extension":358,"meta":359,"navigation":360,"path":361,"seo":362,"source":363,"stem":364,"tags":365,"__hash__":369},"docs\u002Fdocs\u002Fhttp-status-codes.md","HTTP 响应状态码详解",{"type":7,"value":8,"toc":344},"minimark",[9,14,19,30,54,58,63,107,111,117,176,180,188,214,217,297,301,306],[10,11,13],"h1",{"id":12},"http响应状态码","HTTP响应状态码",[15,16,18],"h2",{"id":17},"一临时响应","一、临时响应",[20,21,22,26,27],"p",{},[23,24,25],"strong",{},"1xx","：",[23,28,29],{},"表示临时响应并需要请求者继续执行操作的状态码。",[31,32,33,41,47],"ul",{},[34,35,36,40],"li",{},[37,38,39],"em",{},"100(继续)","    请求者应当继续提出请求。服务器返回此代码表示已收到请求的第一部分，正在等待其余部分。",[34,42,43,46],{},[37,44,45],{},"101(切换协议)","    请求者已要求服务器切换协议，服务器已确认并准备切换。只有在切换新的协议更有好处的时候才应该采取类似措施。",[34,48,49,50,53],{},"102     Processing由WebDAV（RFC2518）扩展的状态码，代表",[37,51,52],{},"处理将被继续执行","。",[15,55,57],{"id":56},"二成功","二、成功",[20,59,60],{},[23,61,62],{},"2xx ：表示成功处理了请求的状态码。",[31,64,65,71,77,83,89,95,101],{},[34,66,67,70],{},[37,68,69],{},"200(成功)","    服务器已成功处理了请求。通常，这表示服务器提供了请求的网页。如果是对robots.txt 文件显示此状态码，则表示 Googlebot 已成功检索到该文件。",[34,72,73,76],{},[37,74,75],{},"201(已创建)","   请求成功并且服务器创建了新的资源。",[34,78,79,82],{},[37,80,81],{},"202(已接受)","    服务器已接受请求，但尚未处理",[34,84,85,88],{},[37,86,87],{},"203(非授权信息)","    服务器已成功处理了请求，但返回的信息可能来自另一来源。",[34,90,91,94],{},[37,92,93],{},"204(无内容)","    服务器成功处理了请求，但没有返回任何内容。",[34,96,97,100],{},[37,98,99],{},"205(重置内容)","    服务器成功处理了请求，但没有返回任何内容。与 204 响应不同，此响应要求请求者重置文档视图(例如，清除表单内容以输入新内容)。",[34,102,103,106],{},[37,104,105],{},"206(部分内容)","    服务器成功处理了部分 GET 请求。",[15,108,110],{"id":109},"三重定向","三、重定向",[20,112,113,116],{},[23,114,115],{},"3xx：要完成请求，需要进一步操作","。通常，这些状态码用来重定向。",[31,118,119,129,135,141,147,153,164,170],{},[34,120,121,122,125,126],{},"Google建议在每次请求中使用重定向不要超过 ",[23,123,124],{},"5","次。可以使用网站管理员工具查看一下 ",[37,127,128],{},"Googlebot  在抓取重定向网页时是否遇到问题。诊断下的网络抓取页列出了由于重定向错误导致   Googlebot   无法抓取的网址。",[34,130,131,134],{},[37,132,133],{},"300(多种选择)","    针对请求，服务器可执行多种操作。服务器可根据请求者 (user agent) 选择一项操作，或提供操作列表供请求者选择。",[34,136,137,140],{},[37,138,139],{},"301(永久移动)","    请求的网页已永久移动到新位置。服务器返回此响应(对 GET 或 HEAD 请求的响应) 时，会自动将请求者转到新位置。应使用此代码告诉某个网页或网站已永久移动到新位置。",[34,142,143,146],{},[37,144,145],{},"302(临时移动)","    服务器目前从不同位置的网页响应请求，但请求者应继续使用原有位置来响应以后的请求。此代码与响应 GET 和 HEAD 请求的 301 代码类似，会自动将请求者转到不同的位置，但不应使用此代码来告诉某个网页或网站已经移动，因为 Googlebot 会继续抓取原有位置并编制索引。",[34,148,149,152],{},[37,150,151],{},"303(查看其他位置)","    请求者应当对不同的位置使用单独的 GET 请求来检索响应时，服务器返回此代码。对于除 HEAD 之外的所有请求，服务器会自动转到其他位置。",[34,154,155,158,159],{},[37,156,157],{},"304(未修改)","    自从上次请求后，请求的网页未修改过。服务器返回此响应时，不会返回网页内容。",[31,160,161],{},[34,162,163],{},"如果网页自请求者上次请求后再也没有更改过，您应将服务器配置为返回此响应(称为 If-Modified-Since HTTP 标头)。服务器可以告诉 Googlebot 自从上次抓取后网页没有变更，进而节省带宽和开销。",[34,165,166,169],{},[37,167,168],{},"305(使用代理)","    请求者只能使用代理访问请求的网页。如果服务器返回此响应，还表示请求者应使用代理。",[34,171,172,175],{},[37,173,174],{},"307(临时重定向)","    服务器目前从不同位置的网页响应请求，但请求者应继续使用原有位置来响应以后的请求。此代码与响应 GET 和 HEAD 请求的 301 代码类似，会自动将请求者转到不同的位置，但您不应使用此代码来告诉 Googlebot 某个页面或网站已经移动，因为 Googlebot 会继续抓取原有位置并编制索引。",[15,177,179],{"id":178},"四请求错误","四、请求错误",[20,181,182,26,185],{},[23,183,184],{},"4xx",[23,186,187],{},"这些状态码表示请求可能出错，妨碍了服务器的处理。",[31,189,190,196,202,208],{},[34,191,192,195],{},[37,193,194],{},"400(错误请求)","    服务器不理解请求的语法。",[34,197,198,201],{},[37,199,200],{},"401(未授权)","    请求要求身份验证。对于登录后请求的网页，服务器可能返回此响应。",[34,203,204,207],{},[37,205,206],{},"403(禁止)","    服务器拒绝请求。可能是服务器或主机拒绝了 Googlebot 访问。",[34,209,210,213],{},[37,211,212],{},"404(未找到)","    服务器找不到请求的网页。例如，对于服务器上不存在的网页经常会返回此代码。",[20,215,216],{},"如果您的网站上没有 robots.txt 文件，而您在 Google 网站管理员工具\"诊断\"标签的 robots.txt 页上看到此状态码，则这是正确的状态码。但是，如果您有 robots.txt 文件而又看到此状态码，则说明您的 robots.txt 文件可能命名错误或位于错误的位置(该文件应当位于顶级域，名为 robots.txt)。如果对于 Googlebot 抓取的网址看到此状态码(在\"诊断\"标签的 HTTP 错误页面上)，则表示 Googlebot 跟随的可能是另一个页面的无效链接(是旧链接或输入有误的链接)。",[31,218,219,225,231,237,243,249,255,261,267,273,279,285,291],{},[34,220,221,224],{},[37,222,223],{},"405(方法禁用)","    禁用请求中指定的方法。",[34,226,227,230],{},[37,228,229],{},"406(不接受)","    无法使用请求的内容特性响应请求的网页。",[34,232,233,236],{},[37,234,235],{},"407(需要代理授权)","    此状态码与 401(未授权)类似，但指定请求者应当授权使用代理。如果服务器返回此响应，还表示请求者应当使用代理。",[34,238,239,242],{},[37,240,241],{},"408(请求超时)","    服务器等候请求时发生超时。",[34,244,245,248],{},[37,246,247],{},"409(冲突)","    服务器在完成请求时发生冲突。服务器必须在响应中包含有关冲突的信息。服务器在响应与前一个请求相冲突的 PUT 请求时可能会返回此代码，以及两个请求的差异列表。",[34,250,251,254],{},[37,252,253],{},"410(已删除)","    如果请求的资源已永久删除，服务器就会返回此响应。该代码与 404(未找到)代码类似，但在资源以前存在而现在不存在的情况下，有时会用来替代404代码。如果资源已永久移动，您应使用301 指定资源的新位置。",[34,256,257,260],{},[37,258,259],{},"411(需要有效长度)","    服务器不接受不含有效内容长度标头字段的请求。",[34,262,263,266],{},[37,264,265],{},"412(未满足前提条件)","    服务器未满足请求者在请求中设置的其中一个前提条件。",[34,268,269,272],{},[37,270,271],{},"413(请求实体过大)","    服务器无法处理请求，因为请求实体过大，超出服务器的处理能力。",[34,274,275,278],{},[37,276,277],{},"414(请求的 URI 过长)","    请求的 URI(通常为网址)过长，服务器无法处理。",[34,280,281,284],{},[37,282,283],{},"415(不支持的媒体类型)","    请求的格式不受请求页面的支持。",[34,286,287,290],{},[37,288,289],{},"416(请求范围不符合要求)","    如果页面无法提供请求的范围，则服务器会返回此状态码。",[34,292,293,296],{},[37,294,295],{},"417(未满足期望值)","    服务器未满足\"期望\"请求标头字段的要求。",[15,298,300],{"id":299},"五服务器错误","五、服务器错误",[20,302,303],{},[23,304,305],{},"5xx：这些状态码表示服务器在处理请求时发生内部错误。这些错误可能是服务器本身的错误，而不是请求出错。",[31,307,308,314,320,326,332,338],{},[34,309,310,313],{},[37,311,312],{},"500(服务器内部错误)","    服务器遇到错误，无法完成请求。",[34,315,316,319],{},[37,317,318],{},"501(尚未实施)","    服务器不具备完成请求的功能。例如，服务器无法识别请求方法时可能会返回此代码。",[34,321,322,325],{},[37,323,324],{},"502(错误网关)","    服务器作为网关或代理，从上游服务器收到无效响应。",[34,327,328,331],{},[37,329,330],{},"503(服务不可用)","    服务器目前无法使用(由于超载或停机维护)。通常，这只是暂时状态。",[34,333,334,337],{},[37,335,336],{},"504(网关超时)","    服务器作为网关或代理，但是没有及时从上游服务器收到请求。",[34,339,340,343],{},[37,341,342],{},"505(HTTP 版本不受支持)","    服务器不支持请求中所用的 HTTP 协议版本。",{"title":345,"searchDepth":346,"depth":346,"links":347},"",3,[348,350,351,352,353],{"id":17,"depth":349,"text":18},2,{"id":56,"depth":349,"text":57},{"id":109,"depth":349,"text":110},{"id":178,"depth":349,"text":179},{"id":299,"depth":349,"text":300},"fundamentals","2024-06-27","按 1xx 到 5xx 分类梳理 HTTP 状态码的含义与典型使用场景。",false,"md",{},true,"\u002Fdocs\u002Fhttp-status-codes",{"title":5,"description":356},null,"docs\u002Fhttp-status-codes",[366,367,368],"http","network","cheatsheet","1D0kXAfAk0CBmkCbUdwdgqHiS6tyew4fOSs89fP9H_g",[371,384,392,398,408,416,423,428,436,441,447,453,460,467,469],{"path":372,"title":373,"description":374,"date":375,"category":376,"tags":377},"\u002Fdocs\u002Ffrontend-coding-standards","前端团队编码规范","HTML \u002F CSS \u002F JavaScript 三端统一的团队编码约定，含缩进、命名、语法与禁用项，可直接作为 Code Review 依据。","2025-12-17","standards",[378,379,380,381,382,383],"html","css","javascript","es6","best-practice","guide",{"path":385,"title":386,"description":387,"date":388,"category":389,"tags":390},"\u002Fdocs\u002Fwindows-mklink","Windows mklink 符号链接用法","mklink 各参数区别与实用场景：目录联接、符号链接与硬链接的选择。","2024-12-18","toolchain",[391,368],"windows",{"path":393,"title":394,"description":395,"date":396,"category":389,"tags":397},"\u002Fdocs\u002Frandom-color-utils","JS 随机颜色生成方法","几种生成随机 RGB \u002F HEX 颜色的实现方式与各自适用场景。","2024-12-11",[380,368],{"path":399,"title":400,"description":401,"date":402,"category":403,"tags":404},"\u002Fdocs\u002Fcanvas-vs-svg","Canvas 与 SVG 绘图方案选型","对比 Canvas 与 SVG 两种绘图方案的优缺点与适用场景，给出选型判断依据。","2024-12-09","visualization",[405,406,407,382],"canvas","svg","performance",{"path":409,"title":410,"description":411,"date":412,"category":389,"tags":413},"\u002Fdocs\u002Ffree-commercial-fonts","免费可商用字体整理","整理思源黑体、思源宋体等可商用中文字体，规避字体版权风险。","2024-11-03",[414,379,415],"font","notes",{"path":417,"title":418,"description":419,"date":412,"category":420,"tags":421},"\u002Fdocs\u002Finterview-browser-network","浏览器与网络考点","从输入 URL 到页面呈现的完整链路，涵盖渲染流程、回流重绘、HTTP 报文与状态码、跨域同源策略与常见攻击方式。","interview",[422,366,367,407,415],"browser",{"path":424,"title":425,"description":426,"date":412,"category":420,"tags":427},"\u002Fdocs\u002Finterview-css-layout","CSS 与布局考点","em 与 rem 的区别、移动端三种适配方案对比、viewport 标准设置与 REM 布局的媒体查询实现。",[379,378,382,415],{"path":429,"title":430,"description":431,"date":412,"category":420,"tags":432},"\u002Fdocs\u002Finterview-framework-tooling","框架与工程化考点","React diff 与 setState 机制、Redux 核心组成、Vue 常考清单，以及 Webpack、Vite、Git 的面试要点。",[433,380,434,435,415],"vue","webpack","vite",{"path":437,"title":438,"description":439,"date":412,"category":420,"tags":440},"\u002Fdocs\u002Finterview-javascript-core","JavaScript 核心考点","数据类型、this 绑定、闭包、原型链、异步与数组方法，前端面试中 JS 部分的高频考点与代码示例。",[380,381,415],{"path":442,"title":443,"description":444,"date":412,"category":354,"tags":445},"\u002Fdocs\u002Fjs-module-systems","JavaScript 模块化方案","梳理 CommonJS、AMD、ES Module 等模块化方案的差异与使用方式。",[380,446,381,415],"module-system",{"path":448,"title":449,"description":450,"date":412,"category":354,"tags":451},"\u002Fdocs\u002Fwebsocket-basics","WebSocket 基础","WebSocket 全双工通信协议的事件、方法与基本用法整理。",[452,367,380,415],"websocket",{"path":454,"title":455,"description":456,"date":457,"category":403,"tags":458},"\u002Fdocs\u002Fgojs-getting-started","GoJS 入门实战","从引入方式、画布初始化到节点模板与数据绑定，一份可直接上手的 GoJS 流程图开发笔记。","2024-08-22",[459,380,415],"gojs",{"path":461,"title":462,"description":463,"date":464,"category":403,"tags":465},"\u002Fdocs\u002Fecharts-options-notes","ECharts 配置项速查","整理 ECharts 常用 option 配置：数据格式、坐标轴、图例与交互项的实际用法。","2024-08-09",[466,380,368],"echarts",{"path":361,"title":5,"description":356,"date":355,"category":354,"tags":468},[366,367,368],{"path":470,"title":471,"description":472,"date":473,"category":354,"tags":474},"\u002Fdocs\u002Fhtml-basics","HTML 基础笔记","HTML 语法规范、常用标签、表格与表单元素速查。","2022-06-10",[378,415,368],1788337378706]