MyBB Internal: One or more warnings occured. Please contact your administrator for assistance.
Chunked Transfer Encoding vs Content-Length
Current time: 03-02-2021, 09:35 PM Hello There, Guest! (LoginRegister)

Post Reply 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Chunked Transfer Encoding vs Content-Length
07-12-2012, 07:55 PM
Post: #1
Chunked Transfer Encoding vs Content-Length
Hello WPT! Recently I've been researching on the difference between chunked transfer encoding vs content-length. I've learned that in chunked transfer encoding, the page is rendered as soon as the first bytes are received, whereas in content-length, it must wait for everything to be downloaded before rendering the page.

Perception is reality. Clearly, chunked transfer encoding would be the winner here. However, I also learned that it has quite a bit of overhead and for large pages, you don't have control of how big each chunk is going to be. I noticed this very site uses nginx and all pages are served with chunked transfer-encoding.

Does anyone have more insights on this? I would love to hear more from you guys. Currently I use lighttpd with defined content length. The pages don't render until all bytes are received, which does feel slower compare some other sites that uses chunked encoding.

Here is my latest test result:
Find all posts by this user
Quote this message in a reply
Post Reply 

Messages In This Thread
Chunked Transfer Encoding vs Content-Length - perry - 07-12-2012 07:55 PM

Forum Jump:

User(s) browsing this thread: 1 Guest(s)