Transfer encoding 'chunked' was introduced with HTTP version 1.1 and is used when the length of the content is not known up-front, so that no 'Content-length' header can be given. Instead the content is sent in several chunks, each prefixed by the length of the chunk.
It is not related to content-encoding like gzip and both can be used together. It is also not related to a content consisting of multiple parts. In this rarely used cases instead a Content-type of multipart/whatever is used and the client has to split the content by the given boundary, similar to multipart MIME messages in mails.
Any HTTP client claiming support for version 1.1 (like LWP) must support this transfer encoding and there is no way to tell the server not to use it except switching to HTTP/1.0. The Accept-Encoding header only affects the accepted values for Content-Encoding (i.e. compression), not Transfer-Encoding.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.