HTTP location
≈ 3 min read
Names in other languages
No names in other languages are held for this entry yet.
Article bodies are English and are not machine-translated. A name in another language is not a translation of the article.
The HTTP Location header field is returned in responses from an HTTP server under two circumstances: #To ask a web browser to load a different web page (URL redirection). In this circumstance, the Location header should be sent with an HTTP status code of 3xx. It is passed as part of the response by a web server when the requested URI has: #* Moved temporarily; #* Moved permanently; or #* Processed a request, e.g. a POSTed form, and is providing the result of that request at a different URI #To provide information about the location of a newly created resource. In this circumstance, the Location header should be sent with an HTTP status code of 201 or 202. An obsolete version of the HTTP 1.1 specifications (IETF RFC 2616) required a complete absolute URI for redirection. The IETF HTTP working group found that the most popular web browsers tolerate the passing of a relative URL and, consequently, the updated HTTP 1.1 specifications (IETF RFC 7231) relaxed the original constraint, allowing the use of relative URLs in Location headers.
The HTTP Location header field is returned in responses from an HTTP server under two circumstances: To ask a web browser to load a different web page (URL redirection). In this circumstance, the Location header should be sent with an HTTP status code of 3xx. It is passed as part of the response by a web server when the requested URI has: Moved temporarily; Moved permanently; or Processed a request, e.g. a POSTed form, and is providing the result of that request at a different URI To provide information about the location of a newly created resource. In this circumstance, the Location header should be sent with an HTTP status code of 201 or 202. An obsolete version of the HTTP 1.1 specifications (IETF RFC 2616) required a complete absolute URI for redirection. The IETF HTTP working group found that the most popular web browsers tolerate the passing of a relative URL and, consequently, the updated HTTP 1.1 specifications (IETF RFC 7231) relaxed the original constraint, allowing the use of relative URLs in Location headers. GET /index.html HTTP/1.1 Host: www.example.com may get the server response HTTP/1.1 302 Found Location: https://www.example.org/index.php HTTP/1.1 302 Found Location: /articles/ The URL of the location is expanded by the client to . HTTP/1.1 302 Found Location: 2020/zoo The client removes the path segment after the last slash of the original URL and appends the relative path resulting in .
Text derived from https://en.wikipedia.org/w/index.php?oldid=1317232210 under CC BY-SA 4.0; modifications have been made.