Talk:Chunked transfer encoding

From Wikipedia, the free encyclopedia
Jump to: navigation, search
WikiProject Computing / Software (Rated Start-class)
WikiProject icon This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
Start-Class article Start  This article has been rated as Start-Class on the project's quality scale.
 ???  This article has not yet received a rating on the project's importance scale.
Taskforce icon
This article is supported by WikiProject Software.
 

Rewrite of examples and explaination of interaction of chunked and gzip encoding[edit]

My (messy) rewrite of specific parts was to:

  • get rid of a bad example (misleading line breaks in 'anatomy' example)
  • explain that the last-chunk is not structurally different from any other chunk, except its zero-length and trailer; the text seemed to indicate that there was a need for yet another trailing CRLF.
  • explain how content-encoding and transfer-encoding interact

Most important though was point 1, as I believe examples should be simple and overly clear, without tricking people into believing there are 2 CRLF's after each chunk-data, with 'content' that contains CRLFs as final bytes in the chunk-data:

--- MISLEADING ---
{hex}
Hello

{hex}
World

{hex}
...

0
"Hello
World
...
"

-

--- BETTER: avoids the problem ---
{hex}
Hello
{hex}
World
{hex}
...
0
"HelloWorld..."

-

--- BEST: shows chunk-data [may] contain linefeeds ---
{hex}
Hello

World
{hex}
...
0
"Hello
World..."

[SOLVED] needs more info about how Content-Encoding (eg: gzip/deflate) is incorporated[edit]

Symbol question.svg Question: Like - are the chunk markers also compressed? are chunks compressed themsevles, or is the entire compressed response compressed prior to chunking? 120.151.160.158 (talk) 10:58, 3 October 2011 (UTC)

The third point in the Rationale section answers that. --Chealer (talk) 04:23, 24 April 2012 (UTC)

Chunked Requests[edit]

My experience shows that servers (IIS, Apache) do not accept chunked requests, even when they produce chunked response. --Javalenok (talk) 10:13, 19 February 2010 (UTC)

Apache does indeed support chunked transfer requests. We are using them for file transfer streaming between backend web apps. 134.115.64.73 (talk) 09:07, 27 May 2011 (UTC)

I don't think chunked requests are possible. I've been trying to do this for a little while and according to http://stackoverflow.com/questions/338624/why-does-iis-not-support-chunked-transfer-encoding it's not possible. —Preceding unsigned comment added by 66.169.13.118 (talk) 15:52, 1 June 2010 (UTC)

Chunked requests ARE possible. We are using chunked transfer requests where I work to support streaming between web apps running under Apache. Maybe IIS does not support Chunked Transfer Encoding for requests, but they are certainly part of the RFC and they certainly work under Apache. 134.115.64.73 (talk) 09:05, 27 May 2011 (UTC)

rename this article[edit]

I would suggest renaming this article to "HTTP_Transfer_Encoding_Chunked" This would make it follow the form that the other HTTP headers articles follow. karlhiramoto (talk) 13:09, 14 May 2010 (UTC)

[SOLVED] Mix with compression[edit]

Removed "Citation needed" in the paragraph about chunked data transfer in combination with deflate compression. Compressing the whole payload results in better compressen, instead of compressing individual chunks. I then performed a test with FireFox 3.6.13 and IE 9 beta. Firefox can handle both, but IE 9 can only understand the data if the payload is compressed as a whole, not as inidiviual chunks. So I removed the "Citation needed" because it may suggest the opposite may also be possible. —Preceding unsigned comment added by 80.136.85.161 (talk) 17:08, 21 January 2011 (UTC)

Sorry but I do not understand why you removed the tag. The statement is still unsourced. I restored it. --Chealer (talk) 04:31, 24 April 2012 (UTC)

Error?[edit]

The chunk length before "pedia" says 6, but "pedia" is only 5 octets long. Is this correct? 88.193.187.93 (talk) —Preceding undated comment added 20:41, 13 July 2012 (UTC)

History/Origin[edit]

I suggest documenting the original Sep 1994 proposal that resulted in this feature[1]

I gather it's not appropriate for me to make the edit as I have a conflict of interest.

DanConnolly (talk) 13:53, 13 September 2013 (UTC)

  1. ^ Connolly, Daniel (27 Sep 1994). "Content-Transfer-Encoding: packets for HTTP". Retrieved 13 September 2013.  Unknown parameter |month= ignored (help)

Added. I’ve always been curious why hexadecimal ended up being used for the chunk length, when decimal numbers are used in other parts of HTTP (Content-Length, range requests etc). I looked through some mail archives from that time but all I could really find were suggestions to use binary (non-ASCII) length encodings. Vadmium (talk, contribs) 02:33, 31 August 2014 (UTC).