W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > May to August 1996

Re: HTTP 1.1 Server Available for Testing

From: Alexei Kosut <akosut@nueva.pvt.k12.ca.us>
Date: Thu, 15 Aug 1996 15:30:29 -0700 (PDT)
To: "John C. Mallery" <jcma@ai.mit.edu>
Cc: "Roy T. Fielding" <fielding@liege.ICS.UCI.EDU>, http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com, bug-cl-http@life.ai.mit.edu, http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
Message-Id: <Pine.HPP.3.95.960815152710.4389A-100000@ace.nueva.pvt.k12.ca.us>
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/1363
On Thu, 15 Aug 1996, John C. Mallery wrote:

> At 1:29 PM -0700 1996-08-15, Roy T. Fielding wrote:
> >Before people start getting jumpy ...
> >
> >The Apache Group is not planning on releasing any server that uses
> >the native HTTP-version "HTTP/1.1" until after the IESG approves the
> >draft for RFC status (i.e., fixes that version in stone).  Since all
> >of the HTTP/1.1 features can be tested as an HTTP/1.0 server (assumimg
> >you are careful not to send HTTP/1.1 features to HTTP/1.0 clients
> >where it is noted in the spec that you MUST not do so), I strongly
> >suggest, for the sake of interoperability, that no application be shipped
> >with the "HTTP/1.1" label until after we all know that there will be
> >no further requirements placed on HTTP/1.1 applications.
> >
> Are you saying that 1.0 clients do not ignore headers they don't understand?
> Or are you trying to say don't send chunked encoded stuff to 1.0 clients?
> I checked every occurence of MUST in the spec to make sure we were conforming,
> and I believe we are.

No, he's saying don't call yourself HTTP/1.1 until there is a HTTP/1.1
spec to ahere to. See, the IESG could come back and say "Whoa,
folks. We'll approve this spec, but only if you add a section that
says every time a request is made, the server MUST send to the
Pentagon, via overnight mail, a hot dog with lots of jalapeno
mustard." Unlikely, but if it happened, you'd have a server that
called itself HTTP/1.1, but was not HTTP/1.1 compliant. Which would be
a bad thing. So until the IESG approves the spec, you need to call
yourself HTTP/1.0.

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 Thursday, 15 August 1996 15:33:32 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:40:17 UTC