blocks|key|3209401|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3209402|301：永久重定向。对此资源进行后续请求的客户端应使用新URI。由于未定义的原因，对于POST/PUT/DELETE+requests.|unordered-list-item|offset|length|style|BOLD|3209403|302：重定向，客户端应该not自动跟随重定向。对此资源进行后续请求的客户端应该使用新的URI而不是。由于未定义的原因，对于POST/PUT/DELETE+requests.|3209404|303：重定向，客户端应该not自动跟随重定向。通常情况下，“操作已完成，请继续其他操作。”对此资源进行后续请求的客户端应该使用新的URI而不是。对于POST/PUT/DELETE请求，客户端应该遵循重定向，但是对于后续的临时重定向，则使用GET。资源可能会在以后返回到此位置。对此资源进行后续请求的客户端应使用旧URI。客户端不应删除POST/PUT/DELETE请求的自动重定向。|3209405|3209406|如果你有选择的话，我个人建议你避免使用302。许多客户在遇到302时并不遵循规范。对于临时重定向，您应该使用303或307，这取决于您希望对非GET请求执行的行为类型。最好是307而不是303，除非你需要POST/PUT/DELETE的替代行为。|3209407|entityMap^0|0|0|3|0|0|3|D|3|1E|11|0|0|5C|0|0|0|3F|0^^$0|@$1|2|3|-4|4|5|6|Q|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|R|7|@$D|S|E|T|F|G]]|8|@]|9|$]]|$1|H|3|I|4|C|6|U|7|@$D|V|E|W|F|G]|$D|X|E|Y|F|G]|$D|Z|E|10|F|G]]|8|@]|9|$]]|$1|J|3|K|4|C|6|11|7|@$D|12|E|13|F|G]]|8|@]|9|$]]|$1|L|3|-4|4|5|6|14|7|@]|8|@]|9|$]]|$1|M|3|N|4|5|6|15|7|@$D|16|E|17|F|G]]|8|@]|9|$]]|$1|O|3|-4|4|5|6|18|7|@]|8|@]|9|$]]]|P|$]]

<ul>
<li>301: Permanent redirect. Clients making subsequent requests for this resource should use the new URI. Clients should not follow the redirect automatically for POST/PUT/DELETE requests.</li>
<li>302: Redirect for undefined reason. Clients making subsequent requests for this resource should not use the new URI. Clients should not follow the redirect automatically for POST/PUT/DELETE requests.</li>
<li>303: Redirect for undefined reason. Typically, 'Operation has completed, continue elsewhere.' Clients making subsequent requests for this resource should not use the new URI. Clients should follow the redirect for POST/PUT/DELETE requests, but use GET for the follow-up request.</li>
<li>307: Temporary redirect. Resource may return to this location at a later point. Clients making subsequent requests for this resource should use the old URI. Clients should not follow the redirect automatically for POST/PUT/DELETE requests.</li>
</ul>

I personally recommend avoiding 302 if you have the choice. Many clients do not follow the spec when they encounter a 302. For temporary redirects, you should use either 303 or 307, depending on what type of behavior you want on non-GET requests. Prefer 307 to 303 unless you need the alternate behavior on POST/PUT/DELETE.

blocks|key|283432|text|303和307之间的区别是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|283433|303：请参阅其他。请求已正确接收，但应使用重定向url上的GET检索结果。|offset|length|style|BOLD|283434|307：临时重定向。整个请求应该被重定向到新的url。任何发布的数据都应该重新发布。|283435|请注意，302的目的是具有307的行为，但大多数浏览器将其实现为303的行为(这两种行为在当时都还不存在)。因此，引入了这两个新代码来取代302。|283436|+301和303之间的区别：|283437|301：文档已移动。将来的请求应该使用新的url。此url已过时。|283438|注意:要小心使用这段代码。浏览器和代理倾向于在其上应用非常积极的缓存，所以如果你回复301，可能需要很长一段时间才能让人重新访问该url。|283439|303：请求接收正确。任何PUT请求都会被处理。所得到的文档可以从重定向url中检索。将来的请求仍然应该转到原始的url。|283440|entityMap^0|0|0|3|0|0|3|0|4|3|0|0|E|0|0|3|0|0|0|3|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@$D|X|E|Y|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|Z|8|@$D|10|E|11|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|12|8|@$D|13|E|14|F|G]]|9|@]|A|$]]|$1|L|3|M|5|6|7|15|8|@$D|16|E|17|F|G]]|9|@]|A|$]]|$1|N|3|O|5|6|7|18|8|@$D|19|E|1A|F|G]]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1B|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|1C|8|@$D|1D|E|1E|F|G]]|9|@]|A|$]]|$1|T|3|-4|5|6|7|1F|8|@]|9|@]|A|$]]]|U|$]]

The difference between 303 and 307 is this:

303: See other. The request is received correctly, but the results should be retrieved using a GET on the redirect url.

307: Temporary redirect. The entire request should be redirected to the new url. Any post data should be re-posted.

Note that 302 was intended to have the behavior of 307, but most browsers implemented it as the behavior of 303 (both of which didn't exist back then). Therefore, those two new codes were introduced to replace 302.

The difference between 301 and 303:

301: The document is moved. Future requests should use the new url. This url is obsolete. 

Note: Be careful with this code. Browsers and proxies tend to apply really agressive caching on it, so if you reply with a 301 it might take a long while for someone to revisit that url.

303: The request is received correctly. Any PUT requests are processed. The resulting document can be retrieved from the redirect url. Future request should still go to the original url.

The differences between the various HTTP 3XX redirect codes are not clear to me. Yes, I've read the spec, but there seems to be some discrepancy between the standard and actual practice here.

The <code>301</code> redirect code seems clear enough: This means the resource was permanently moved to another URI, and future requests should use that URI.

And the <code>307</code> redirect code also seems clear: it means the redirect is temporary, and future requests should still use the original URI.

But I can't tell what the difference is between <code>302</code> and <code>303</code>, or why either of them are really different from <code>301</code>. It seems that <code>302</code> was originally intended to be a temporary redirect, (like <code>307</code>), but in practice, most browsers treated it like a <code>303</code>. But what's the difference between a <code>303</code> and a <code>301</code>? Is <code>301</code> supposed to mean the redirect is more permanent?

Difference between HTTP redirect codes

不同的HTTP 3XX重定向代码之间的区别我不清楚。是的，我已经阅读了规范，但这里的标准和实际操作之间似乎存在一些差异。301重定向代码似乎足够清楚:这意味着资源被永久地移动到另一个URI，并且将来的请求应该使用该URI。而且307重定向代码似乎也很清楚:它意味着重定向是临时的，将来的请求应该仍然使用原始URI。但我不...

问HTTP重定向代码之间的差异
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问HTTP重定向代码之间的差异EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问HTTP重定向代码之间的差异
EN