[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: read-response-body of (web response) depends on Content-Length but .
Re: read-response-body of (web response) depends on Content-Length but ...
Fri, 27 Apr 2012 19:32:15 +0800
On 27 April 2012 16:28, Sunjoong Lee <address@hidden> wrote:
> I googled and found http://tools.ietf.org/html/rfc2616 .
> In a section of "4.4 Message Length":
> 2.If a Transfer-Encoding header field (section 14.41) is present and
> has any value other than "identity", then the transfer-length is
> defined by use of the "chunked" transfer-coding (section 3.6),
> unless the message is terminated by closing the connection.
> 3.If a Content-Length header field (section 14.13) is present, its
> decimal value in OCTETs represents both the entity-length and the
> transfer-length. The Content-Length header field MUST NOT be sent
> if these two lengths are different (i.e., if a Transfer-Encoding
> header field is present). If a message is received with both a
> Transfer-Encoding header field and a Content-Length header field,
> the latter MUST be ignored.
Ian Price has done some work to support chunked encoding recently,
which seems to be the source of your problems. His solution was
already quite thorough but some comments were made. You may want to
help finishing that off.
Search the guile-devel and -user archives for "Chunked Encoding" to find it.