HTTP 1.1 - Can a client request that transfers not be "chunked"?

http chunked-encoding chunked http-1.1 http-chunked
Matt picture Matt · May 21, 2014 · Viewed 8.3k times · Source

Is it possible for a HTTP 1.1 client to set a header value that indicates the responses to requests should not be chunked? Or is the only way to prevent this, is to send a HTTP 1.0 request? I've tried googling around, but all I can find is ways to disable chunked transfers on HTTP 1.1 servers, so I am guessing it is not possible on a client, but I thought I'd ask anyways.

Answer

Julian Reschke picture Julian Reschke · May 21, 2014

In HTTP (starting with HTTP/1.1), recipients MUST support chunked encoding. See http://greenbytes.de/tech/webdav/draft-ietf-httpbis-p1-messaging-26.html#rfc.section.4.1.p.4.

Related questions

difference between multipart and chunked protocol

Can some experts explain the differences between the two? Is it true that chunked is a streaming protocol and multipart is not? What is the benefit of using multipart?

Read More
Java HTTP server sending chunked response

I am working on a Java application which has a built in HTTP server, at the moment the server is implemented using ServerSocketChannel, it listens on port 1694 for requests: msvrCh = ServerSocketChannel.open(); msvrCh.socket().bind(new InetSocketAddress(mintPort)); msvrCh.configureBlocking(…

Read More
Content-Length header versus chunked encoding

I'm trying to weigh the pros and cons of setting the Content-Length HTTP header versus using chunked encoding to return [possibly] large files from my server. One or the other is needed to be compliant with HTTP 1.1 specs using persistent …

Read More