HEAD method requests the headers that are returned if the specified resource would be requested with an HTTP
GET method. Such a request can be done before deciding to download a large resource to save bandwidth, for example.
A response to a
HEAD method should not have a body. If so, it must be ignored. Even so, entity headers describing the content of the body, like
Content-Length may be included in the response. They don't relate to the body of the
HEAD response, which should be empty, but to the body of similar request using the
GET method would have returned as a response.
If the result of a
HEAD request shows that a cached resource after a
GET request is now outdated, the cache is invalidated, even if no
GET request has been made.
|Request has body||No|
|Successful response has body||No|
|Allowed in HTML forms||No|
|RFC 7231, section 4.3.2: HEAD||Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content|
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.
|Chrome||Edge||Firefox||Internet Explorer||Opera||Safari||Android webview||Chrome for Android||Edge Mobile||Firefox for Android||Opera for Android||iOS Safari||Samsung Internet|
|Basic support||Chrome Full support Yes||Edge Full support Yes||Firefox Full support Yes||IE Full support Yes||Opera Full support Yes||Safari Full support Yes||WebView Android Full support Yes||Chrome Android Full support Yes||Edge Mobile Full support Yes||Firefox Android Full support Yes||Opera Android Full support Yes||Safari iOS Full support Yes||Samsung Internet Android Full support Yes|
- Full support
- Full support