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

Re: IPP> Chunked POST

From: <kugler@us.ibm.com>
Date: Fri, 20 Aug 1999 12:10:28 -0600
To: http-wg@cuckoo.hpl.hp.com
Message-ID: <872567D3.0063E8D5.00@d53mta08h.boulder.ibm.com>
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/538

I don't want to implement a new protocol service using CGI.  But I'm worried
about things like proxies refusing to forward chunked requests.

I haven't kept up with the Jakarta thing, but it will be interesting to see if
the Apache Java servlet implementation supports chunked POST.


"Roy T. Fielding" <fielding@kiwi.ics.uci.edu> on 08/20/99 11:47:01 AM

To:   Carl Kugler/Boulder/IBM@IBMUS
cc:   http-wg@cuckoo.hpl.hp.com
Subject:  Re: IPP> Chunked POST

>> Nobody is going to prevent you from building a server that responds with
>> 411 to every request without implementing chunked.  It would be a dumb
>> thing to do, but the standard doesn't prevent people from doing dumb things
>> (only things that won't interoperate with others via HTTP).
>Isn't that what Apache does with chunked POSTs?

No.  It is what mod_cgi requires.  Apache implements chunked in the core,
where any module can make use of it if they so desire.

As I've said many times before, implementing a new protocol service
using CGI is a bad idea.  Making HTTP requirements based on the limitations
of CGI is even worse.

Received on Friday, 20 August 1999 19:22:15 UTC

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