How does the HEAD/GET requests work ?
Robert H. Terry
rhterry at RBSE.Mountain.Net
Wed Jan 24 14:27:58 EST 1996
As part of a library interoperability standard I am working on, I am
proposing using the optional META tags in HTML 2.0 Head part. The
specifications state the META tag has two main functions:
- to provide a means to discover that the data set exists and how it
might be obtained or accessed; and
- to document the content, quality, and features of a data set,
indicating its fitness for use.
Which fits well with our needs for library interoperation needs. Later,
in the specifications it uses the following example:
If the document contains:
<META HTTP-EQUIV="Expires"
CONTENT="Tue, 04 Dec 1993 21:29:02 GMT">
<meta http-equiv="Keywords" CONTENT="Fred">
<META HTTP-EQUIV="Reply-to"
content="fielding at ics.uci.edu (Roy Fielding)">
<Meta Http-equiv="Keywords" CONTENT="Barney">
then the server may include the following header fields:
Expires: Tue, 04 Dec 1993 21:29:02 GMT
Keywords: Fred, Barney
Reply-to: fielding at ics.uci.edu (Roy Fielding)
as part of the HTTP response to a `GET' or `HEAD' request for that
document.
My question, is how does this work ? Can an Agent/Browser search/browse
the Head of docuemnts only ? Are there benefits real/intended in doing
same ? Does anyone have any other thoughts on the whole subject ?
Thanks in advance,
Bob Terry
http://rbse.mountain.net/MOREplus/
800-846-1458 x 18
More information about the Web4lib
mailing list