Webmasters Stack Exchange is a question and answer site for pro webmasters. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

How to avoid chunked Transfer-Encoding ? Is there any benefit with this encoding?

Below is what appears as part of Apache Web Server (V2.4) header message:

Connection:  Keep-Alive
Content-Type:    text/html; charset=utf-8
Content-Encoding:    gzip
Transfer-Encoding:   chunked
share|improve this question
If you don't even know what it is, why do you want to avoid this value for it? And what other value do you want? Why? – Su' Dec 8 '12 at 11:11
up vote 0 down vote accepted

Chunked transfer encoding is an HTTP/1.1 feature that enables keep-alive requests.

If you want to avoid chunked encoding send requsets to the server using HTTP/1.0. A request with HTTP/1.0 would look like this

GET /index.html HTTP/1.0
Host: www.example.com

The problem with HTTP/1.0 is that it required a new connection for each resource downloaded. Since each html document contains many images, css, and js files, you might need tens of connection to download an entire page using HTTP/1.0. Establishing each connection is slow. When HTTP/1.1 was invented, a design goal was to allow pipelining and re-use of connections. Now browsers can download the page and all of its images in a single connection. The webserver responds in "chunks". Each chunk starts with the size of the chunk. Once that size has been downloaded, the browser can make another request on the same connection and receive more chunked data without starting up a new connection.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.