W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2010

Re: clarification of 7.2.2. Monitoring Connections for Error Status Messages

From: Henrik Nordström <henrik@henriknordstrom.net>
Date: Tue, 04 May 2010 01:53:05 +0200
To: Wenbo Zhu <wenboz@google.com>
Cc: Jamie Lokier <jamie@shareable.org>, Mark Nottingham <mnot@mnot.net>, ietf-http-wg@w3.org
Message-Id: <1272930785.24081.83.camel@localhost.localdomain>
tis 2010-04-20 klockan 01:54 -0700 skrev Wenbo Zhu:

> IMO, early non-error response does seem to violate the basic RPC
> scheme that is assumed in HTTP. From reading the charter of this WG, I
> am not sure if we choose to allow, explicitly, such interaction
> semantics, will it introduce any incompatibility?

Any change which will REQUIRE clients to continue sending their request
body even after the server have responded will introduce

> Non-error status doesn't necessarily guarantee a complete/successful
> response, e.g. server processing, networking may fail any way.. The
> real issue is that clients/proxies alike need be prepared to receive
> responses when requests are still under transmission.

Which most do.

But they also must be prepared to continue sending the request, which is
not in line with current specifications.

Received on Monday, 3 May 2010 23:53:41 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:10:53 UTC