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

Re: #300: Define non-final responses

From: Poul-Henning Kamp <phk@phk.freebsd.dk>
Date: Sun, 17 Jul 2011 06:32:01 +0000
To: Mark Nottingham <mnot@mnot.net>
cc: HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <19819.1310884321@critter.freebsd.dk>
In message <6D4B566E-F7D6-4539-AEDC-E38BA3BB94CF@mnot.net>, Mark Nottingham wri
tes:
><http://trac.tools.ietf.org/wg/httpbis/trac/ticket/300>
>
>1xx responses are non-final; i.e., the underlying model is that for each =
>request, there are 0 to many non-final responses, and exactly one final =
>response.

But with the footnote that 101 is final as far as HTTP goes, and that
it is up to the new protocol to define who sends something next.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.
Received on Sunday, 17 July 2011 06:32:26 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:45 GMT