- From: Ben Laurie <ben@algroup.co.uk>
- Date: Wed, 16 Dec 1998 23:15:30 +0000
- To: Larry Masinter <masinter@parc.xerox.com>
- Cc: Carl Kugler <kugler@us.ibm.com>, CGI-WG@golux.com, http-wg@cuckoo.hpl.hp.com, ipp@pwg.org
Larry Masinter wrote: > > > Many http server implementors seem to have interpreted the combination > > of these requirements to imply that a POST request without a > > Content-Length HTTP header cannot have a message-body. > > This implication might have held for HTTP/1.0, but is wrong for HTTP/1.1. > > > Indeed, I have tried several commercial web servers and > > in all cases, a servlet or CGI program gets end-of-file as soon as it > > tries to read the message-body input stream for a POST request with > > chunked transfer-coding. > > Did these servers purport to support HTTP/1.1 for CGI scripts? > http://www.w3.org/Protocols/HTTP/Forum/Reports/ is a survey of > implementations, but we didn't ask implementations to distinguish > whether they supported 'chunked' transfer encoding specifically. > > In any case, you left out the most obvious solution: don't use 'CGI' > to implement IPP. > > However, it would be useful to update CGI for HTTP/1.1. Hmm. I'm pretty sure Apache works correctly in this case, but I doubt it has been heavily tested. Does anyone know different? Cheers, Ben. -- Ben Laurie |Phone: +44 (181) 735 0686| Apache Group member Freelance Consultant |Fax: +44 (181) 735 0689|http://www.apache.org/ and Technical Director|Email: ben@algroup.co.uk | A.L. Digital Ltd, |Apache-SSL author http://www.apache-ssl.org/ London, England. |"Apache: TDG" http://www.ora.com/catalog/apache/
Received on Wednesday, 16 December 1998 15:20:40 UTC