[10518] in www-talk@info.cern.ch

home help back first fref pref prev next nref lref last post

Re: Call for Closure - HTTP response version

daemon@ATHENA.MIT.EDU (Koen Holtman)
Wed Jan 1 09:19:45 1997

From: koen@win.tue.nl (Koen Holtman)
To: dwm@xpasc.com (David W. Morris)
Date: Wed, 1 Jan 1997 15:11:54 +0100 (MET)
Cc: akosut@nueva.pvt.k12.ca.us, koen@win.tue.nl, dmk@research.bell-labs.com,
        http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com, www-talk@www10.w3.org,
        http-wg@cuckoo.hpl.hp.com
In-Reply-To: <Pine.GSO.3.95.961231163936.27146A-100000@shell1.aimnet.com> from "David W. Morris" at Dec 31, 96 04:43:32 pm

David W. Morris:
>
[...]
>Another choice is to stop overloading a single value for two 
>purposes ...
>  1.  Declaring the servers capabilities
>  2.  Labeling the level of the response

I see no such overloading in the HTTP/1.1 spec.  The spec is clear on
the fact that the minor version number in the response does 1 (but
only for this particular request!), not 2.

Now, there *might* be a good reason to add a header which does 2.  A
header which says `this response is compatible with both 1.0 clients
and 1.1 clients' might be useful for a 1.1 caching proxy.  We'll find
out when someone actually starts trying to build such a proxy.

>Dave Morris 

Koen.


home help back first fref pref prev next nref lref last post