W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 1996

Re: issue: what version?

From: Alexei Kosut <akosut@nueva.pvt.k12.ca.us>
Date: Tue, 3 Dec 1996 13:22:46 -0800 (PST)
To: Dave Kristol <dmk@research.bell-labs.com>
Cc: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
Message-Id: <Pine.HPP.3.95.961203131713.10983A-100000@ace.nueva.pvt.k12.ca.us>
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/2024
On Tue, 3 Dec 1996, Dave Kristol wrote:

> I don't recall whether the following issue was resolved on the mailing list:

As I recall, it was discussed, but not resolved.

> What protocol version number should an HTTP/1.1-compliant origin server
> send for an HTTP/1.0 request?
> There seemed to be two camps:
> 1) Send HTTP/1.0 as the response to HTTP/1.0 requests (and HTTP/1.1 as the
> 	response to HTTP/1.1 requests).
> 	Pro:	HTTP/1.0 clients may only understand HTTP/1.0 responses

There are very few clients that do this - probably about the same as
the number of servers that can't understand HTTP/1.1 requests.

> 	Con:	a client would never be able to determine whether a server
> 		understands HTTP/1.1
> 2) Send HTTP/1.1 responses always.
> 	Pro:	the server advertises its capability
> 	Con:    because the response (headers) must be HTTP/1.0
> 		compatible, the server is "lying" about the kind of
> 		response and may mislead or confuse the client.

IMHO, HTTP/1.0 and HTTP/1.1 are close enough in form that it is quite
possible to craft a HTTP/1.1 response that is completely compatible
with HTTP/1.0. Apache 1.2 (a public beta of which was just released)
follows this approach.

Alexei Kosut <akosut@nueva.pvt.k12.ca.us>      The Apache HTTP Server
URL: http://www.nueva.pvt.k12.ca.us/~akosut/   http://www.apache.org/
Received on Tuesday, 3 December 1996 13:36:12 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 2 February 2023 18:43:00 UTC