Lines Matching full:chunked
347 with a resource that returns chunked-encoded _and_ with a Content-Length
464 chunked-encoding trailer.
968 "Transfer-Encoding: chunked" enforced. I would then cause the first request
1335 protocols by abusing chunked transfer encoding in both the HTTP request and
2751 - Detect cases where an upload must be sent chunked and the server supports
2805 scenario of sending chunked data to a HTTP 1.0 server. All these fail
2921 Transfer-Encoding: chunked header which is illegal. This test case is
4072 - I fixed two cases of missing return code checks when handling chunked
4476 - libcurl now handles chunked-encoded CONNECT responses
4956 chunked encoding (that also lacks "Connection: close"). It now simply
5155 responses without Content-Length or chunked encoding as without bodies. We
5493 chunked encoding:
5494 * Added states to chunked parsing for final CRLF
5496 * Moved chunked header initializing to a spot just before receiving
5819 response has been taken care of) must have Content-Length or chunked
5834 dealing with HTTP chunked encoding.
6148 - Mark Lentczner fixed how libcurl was not properly doing chunked encoding
6149 if the header "Transfer-Encoding: chunked" was set by the application.
7070 finding the end of a chunked-encoded POST too early.
7208 - Adrian Schuur added trailer support in the chunked encoding stream. The
7211 contains a flawed chunked encoding stream that still works the same.
7433 complained on the chunked encoding, even though a HEAD should never return a
7434 body and thus it cannot be a chunked-encoding problem!
8118 - Bug report #1078066: when a chunked transfer was pre-maturely closed exactly
8810 the size of the upload and chunked transfer-encoding can only be used on
9752 doing chunked encoding, which current curl cannot do even if you disable
9753 the transfer-encoding chunked header. Now it can again, and test case 98
9816 read callback, with chunked transfer-encoding.
9840 - Richard Bramante fixed chunked transfer-encoded "uploads" to send a final
10030 when Transfer-Encoding: chunked is used, as mandated by RFC2616.
10634 with FOLLOWLOCATION and chunked transfer-encoding, as libcurl would not
11117 when deflate or gzip contents were downloaded using chunked encoding.
11617 enables a plain HTTP POST to be sent chunked if we want to. This also
11676 "Transfer-Encoding: chunked", it will now enable a chunked transfer.
11678 Also, chunked transfer didn't quite work before but seems to do so now.
11716 Transfer-Encoding: chunked.
14244 - Cris Bailiff fixed a chunked transfer encoding problem with persistent
14246 chunked and non-chunked transfers.
14573 chunked transfer-encoding. Given his fine example-site, I could easily spot
14600 - Made the chunked transfer-encoding engine detected bad formatted data length
14644 - "Transfer-Encoding: chunked" is no longer any trouble for libcurl. I've
