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

Re: IPP> Chunked POST

From: <kugler@us.ibm.com>
Date: Thu, 19 Aug 1999 08:50:00 -0600
To: "Roy T. Fielding" <fielding@kiwi.ics.uci.edu>
cc: Larry Masinter <masinter@parc.xerox.com>, "Yaron Goland (Exchange)" <yarong@exchange.microsoft.com>, http-wg@hplb.hpl.hp.com
Message-ID: <872567D2.00518E4C.00@d53mta08h.boulder.ibm.com>
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/535

Right, a client can interoperate with any server as long as it sticks to
Content-Length.  But if it cannot determine the message length in advance it's
probably SOL.


"Roy T. Fielding" <fielding@kiwi.ics.uci.edu> on 08/18/99 11:59:21 PM

To:   Larry Masinter <masinter@parc.xerox.com>
cc:   Carl Kugler/Boulder/IBM@IBMUS, "Yaron Goland (Exchange)"
      <yarong@exchange.microsoft.com>, http-wg@hplb.hpl.hp.com
Subject:  Re: IPP> Chunked POST

>We might make replying '411 and connection close' to a chunked encoding
>'conditionally compliant' rather than 'compliant' because otherwise,
>as has been pointed out, there are inteorperability problems.

There is no interoperability problem here.  The server response is
understandable by the client.  Any server has the right to deny
service rather than buffer an unknown amount of data.  No change is
needed to the spec.

Received on Thursday, 19 August 1999 07:57:17 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 2 February 2023 18:43:06 UTC