HTTP

Persistence · Compression · HTTP Secure

Headers

ETag · Cookie · Referrer · Location

Status codes

301 Moved permanently

302 Found

303 See Other

403 Forbidden

404 Not Found

This box: view • talk • edit

The HTTP Location header is used to force a web browser to reload a different web page. It is passed as part of the Server Response by a web server when the requested URL has:

• Moved temporarily
• Moved permanently, or
• A new resource has been created

The HTTP Location header should be sent with a HTTP Response Code of 3xx.

While the internet standard RFC 1945 (HTTP 1.0) requires a complete URL for redirection^[1][2], the most popular web browsers support the passing of a Relative URL as the value for a Location: header.^{[citation needed]}

Contents 1 Example 2 Relative URL Example 3 Notes 4 References 5 See also

[edit] Example

The internet standard requires an absoluteURI token to follow a Location: header, which means it must contain a scheme (http:// or https://), web server address, and a path of the new web address.

Client request:

 GET /index.html HTTP/1.1 Host: www.example.com 

Server response:

 HTTP/1.1 302 Found Location: http://www.wikipedia.org/index.php 

[edit] Relative URL Example

This example, while incorrect based on the internet standard^[3], works in all popular browsers.^{[citation needed]}

Client request:

 GET /blog HTTP/1.1 Host: www.example.com 

Server response:

 HTTP/1.1 302 Found Location: /blog/ 

[edit] Notes

Not to be confused with JavaScript location variable.

[edit] References

1. ^ RFC 2616 (HTTP 1.1)
2. ^ RFC 1945 (HTTP 1.0)
3. ^ http://tools.ietf.org/html/rfc2616#section-14.30

[edit] See also

• Hypertext Transfer Protocol
• List of HTTP status codes
• List of HTTP headers