W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2014

100 Continue editorial comment

From: Greg Wilkins <gregw@intalio.com>
Date: Tue, 5 Aug 2014 16:13:01 +1000
Message-ID: <CAH_y2NF4TD7HnZ90MZOUdwMw7zrThyacujXXkuxjEvccy3BREw@mail.gmail.com>
To: HTTP Working Group <ietf-http-wg@w3.org>
Just implementing 100 continues support and realise we need another
exception to Malformed Requests:

In http://tools.ietf.org/html/draft-ietf-httpbis-http2-14#section-8.1.2.6,
the text says:

   A request or response that includes an entity body can include a
   "content-length" header field.  A request or response is also
   malformed if the value of a "content-length" header field does not
   equal the sum of the DATA frame payload lengths that form the body,
   with the exception of responses to HEAD requests, which always
   contain no DATA frames.

I believe that we also need to add an exception for requests that are
expecting 100 continues but that receive another response.   In HTTP/1.1,
that would cause the connection to be closed, but in HTTP/2 I assume it
will mean the client should just close the stream (empty DATA frame with
END_STREAM flag?).

So perhaps the text should be something like:

   A request or response that includes an entity body can include a
   "content-length" header field.  A request or response is also
   malformed if the value of a "content-length" header field does not
   equal the sum of the DATA frame payload lengths that form the body,
   with the exception of:

    * responses to HEAD requests, which always contain no DATA frames.

    * request that were expecting a 100 Continue but received a
terminal response.


cheers


-- 
Greg Wilkins <gregw@intalio.com>
http://eclipse.org/jetty HTTP, SPDY, Websocket server and client that scales
http://www.webtide.com  advice and support for jetty and cometd.
Received on Tuesday, 5 August 2014 06:13:29 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 30 March 2016 09:57:09 UTC