Re: HEAD instead of GET??
| From: | Jason Brooke | Date: | Tue, 28 Aug 2001 17:08:15 +0000 |
| Subject: | Re: HEAD instead of GET?? | ||
| References: | 1 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-64848@lists.php.net to get a copy of this message | ||
> For example:
>
> HEAD /contact.php4 HTTP/1.0
>
> instead of
>
> GET /contact.php4 HTTP/1.0
>
>
>
>
> What does it mean?
>
> cheers,
>
> - seb
From the http1.1 rfc (because it's a http-related thing, not php)
ftp://ftp.isi.edu/in-notes/rfc2616.txt
9.4 HEAD
The HEAD method is identical to GET except that the server MUST NOT
return a message-body in the response. The metainformation contained
in the HTTP headers in response to a HEAD request SHOULD be identical
to the information sent in response to a GET request. This method can
be used for obtaining metainformation about the entity implied by the
request without transferring the entity-body itself. This method is
often used for testing hypertext links for validity, accessibility,
and recent modification.
The response to a HEAD request MAY be cacheable in the sense that the
information contained in the response MAY be used to update a
previously cached entity from that resource. If the new field values
indicate that the cached entity differs from the current entity (as
would be indicated by a change in Content-Length, Content-MD5, ETag
or Last-Modified), then the cache MUST treat the cache entry as
stale.