W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > January to April 1997

Re: 1xx Clarification

From: Scott Lawrence <lawrence@agranat.com>
Date: Mon, 14 Apr 1997 08:59:55 -0400
Message-Id: <199704141259.IAA08148@devnix.agranat.com>
To: http-wg@cuckoo.hpl.hp.com
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/3027

>>>>> "RF" == "Roy T Fielding" <fielding@kiwi.ICS.UCI.EDU> writes:

RF> The 100 response must be sent by an HTTP/1.1 server upon receipt of
RF> any HTTP/1.1 request containing a message body, after it receives the
RF> header fields and determines that it wishes to receive that body.  The
RF> RFC 2068 says this in section 8.2, but in a rather confusing way.

RF> The client should not care either, since it should be ignoring any
RF> 1xx class of response.  A client that is not looking for such a response
RF> will simply see it (and ignore it) upon its next request, or never see
RF> it at all if it just drops the connection.

  Our server does send a 100 Continue under those conditions; the rule
  I would like to see stated more directly is that:

    When sending a request with a body to a server it has reason to
    believe implements HTTP/1.1, a client SHOULD send the headers and
    then wait for a 100 Continue or an error status before
    transmitting the body of the request.

  the current spec essentially says this only for the case where the
  client is retrying a request, not for the first attempt.

Scott Lawrence                                       <lawrence@agranat.com>
Agranat Systems, Inc.                               http://www.agranat.com/
Received on Monday, 14 April 1997 06:01:51 UTC

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