[7050] in www-talk@info.cern.ch
Re: Draft 01 of HTTP/1.0
daemon@ATHENA.MIT.EDU (Paul Burchard)
Mon Dec 19 19:25:58 1994
Date: Tue, 20 Dec 1994 01:15:49 +0100
Errors-To: listmaster@www0.cern.ch
Reply-To: burchard@horizon.math.utah.edu
From: Paul Burchard <burchard@horizon.math.utah.edu>
To: Multiple recipients of list <www-talk@www0.cern.ch>
A couple of questions and comments on the new HTTP/1.0 spec...
(1) In the definition of the Accept request header, there is no
mention of a "version" modifier, e.g.,
Accept: text/html; version=3.0
This would seem like the right way to determine HTML client
capabilities. Going by the User-Agent field is a real quagmire.
(2) The semantics of Expires should discourage clients from
_indiscriminately_ trying to refetch objects, just because they have
expired. Dynamically-created pages can be ephemeral, without having
time-dependent content that needs to be updated.
For example, the Geometry Center interactive gallery generates
dynamic graphical HTML pages customized to each user's request. The
user's images are deleted at the same moment they are fetched, and so
the document ceases to exist on the server the moment it is
retrieved. Therefore, the gallery expires all documents immediately:
Expires: Sun, 01 Jan 0000 00:00:00 GMT
Nevertheless, it would not make sense to try to fetch an "updated"
version of such a document.
--------------------------------------------------------------------
Paul Burchard <burchard@math.utah.edu>
``I'm still learning how to count backwards from infinity...''
--------------------------------------------------------------------
