Location response header indicates the URL to redirect a page to. It only provides a meaning when served with a
3xx (redirection) or
201 (created) status response.
In cases of redirection, the HTTP method used to make the new request to fetch the page pointed to by
Location depends of the original method and of the kind of redirection:
303(See Also) responses always lead to the use of a
307(Temporary Redirect) and
308(Permanent Redirect) don't change the method used in the original request;
301(Permanent Redirect) and
302(Found) doesn't change the method most of the time, though older user-agents may (so you basically don't know).
All responses with one of these status codes send a
In cases of resource creation, it indicates the URL to the newly created resource.
Content-Location are different:
Location indicates the target of a redirection (or the URL of a newly created resource), while
Content-Location indicates the direct URL to use to access the resource when content negotiation happened, without the need of further content negotiation.
Location is a header associated with the response, while
Content-Location is associated with the entity returned.
|Header type||Response header|
|Forbidden header name||no|
- A relative (to the request URL) or absolute URL.
|RFC 7231, section 7.1.2: Location||Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content|
|RFC 2616, section 14.30: Location (Obsolete)||Hypertext Transfer Protocol -- HTTP/1.1|
The compatibility table in this page is generated from structured data. If you'd like to contribute to the data, please check out https://github.com/mdn/browser-compat-data and send us a pull request.
|Feature||Android webview||Chrome for Android||Edge mobile||Firefox for Android||Opera Android||iOS Safari||Samsung Internet|