IPP> Chunked POST: SUMMARY

IPP> Chunked POST: SUMMARY

IPP> Chunked POST: SUMMARY

kugler at us.ibm.com kugler at us.ibm.com
Wed Jan 6 19:23:35 EST 1999



Ross Patterson wrote:
>
>>...
>>5.  Origin servers MUST remove the Transfer-Encoding before passing a
>>request body to a plug-in, servlet, (Fast)CGI, or across any other
gateway
>>boundary.
>
>That's not clearly stated in either the HTTP 1.1 or CGI 1.1
specifications.

An unfortunate omission, IMO.

...
>
>HTTP actually doesn't guarantee anything about *acceptance* of requests.
>There are lots of conditions that can provoke responses other than
>"200 OK".  It does, however, require that all HTTP 1.1 applications be
>able to receive and decode chunked requests (HTTP 1.1 rev 6, sec. 3.6.1).
>If the resource in question is implemented via CGI 1.1, it might still
>be rejected as you noted due to buffering concerns, but if it is
>implemented via an interface that does not require a pre-determined
>length, there's nothing wrong with sending chunked data.
>

Section 4.4 says:

> All HTTP/1.1 applications that receive entities MUST accept the
> "chunked" transfer-coding (section 3.6), thus allowing this mechanism
> to be used for messages when the message length cannot be determined
> in advance.

Apparently that should be interpreted as "MUST accept the 'chunked'
TRANSFER-CODING, but NEED NOT accept REQUESTs with that transfer-coding."


        -Carl





More information about the Ipp mailing list