Received: by taz.hyperreal.com (8.7.6/V2.0) id JAA15069;
 Wed, 9 Oct 1996 09:57:17 -0700 (PDT)
Received: from creche.cygnus.com by taz.hyperreal.com (8.7.6/V2.0) with SMTP
 id JAA15046; Wed, 9 Oct 1996 09:57:04 -0700 (PDT)
Received: (from tromey@localhost) by creche.cygnus.com (8.6.12/8.6.9) id
 KAA03592; Wed, 9 Oct 1996 10:54:27 -0600
To: new-httpd@hyperreal.com
Subject: Re: 411 Length Required response to HTTP/1.0 request
References: <199610091258.IAA02292@breckenridge.openmarket.com>
X-Zippy: Awright, which one of you hid my PENIS ENVY?
X-Attribution: Tom
From: Tom Tromey <tromey@creche.cygnus.com>
Date: 09 Oct 1996 10:54:26 -0600
In-Reply-To: Mark Brown's message of Wed, 09 Oct 1996 08:58:08 -0400
Message-ID: <m13ezom62l.fsf@creche.cygnus.com>
Lines: 23
X-Mailer: Red Gnus v0.34/Emacs 19.34
Sender: owner-new-httpd@apache.org
Precedence: bulk
Reply-To: new-httpd@hyperreal.com

Mark> Content-length was optional in HTTP/1.0.

The HTTP/1.0 standard says:

   A valid <CODE>Content-Length</CODE> is required on all HTTP/1.0
   <CODE>POST</CODE> requests. An HTTP/1.0 server should respond with
   a 400 (bad request) message if it cannot determine the length of
   the request message's content.

Elsewhere it says that the only difference between PUT and POST is one
of interpretation.

Here is some text from another part of the standard:

 A valid <CODE>Content-Length</CODE> field value is required on all 
 HTTP/1.0 request messages containing an entity body.

So I'd say that Content-Length is in fact required.

Tom
-- 
tromey@cygnus.com                 Member, League for Programming Freedom