Article ID: 278998 - View products that this article applies to.
This article was previously published under Q278998
This article describes how to enable chunked transfer encoding with Internet Information Services (IIS).
The HTTP specification does not provide a way to guarantee reliable transmission of replies. The HTTP 1.1 specification adds transfer encoding as a way to make it possible to safely transport messages that are sent through HTTP (see RFC 2068). "Chunked" is a type of transfer encoding by which the message body is transmitted to the client as chunks that are stamped with the size of the chunks (see section 14.40 of RFC 2068). With chunked transfer encoding, the client can make sure that it has received all of the data that the server sends.
Chunked transfer encoding is similar to MIME encoding in relation to Internet mail (see RFC 822). The specific differences between MIME encoding and chunked transfer encoding are discussed in section 19.4 of RFC 2068.
For more information, visit the following RFC Web sites:
RFC 1945: Hypertext Transfer Protocol -- HTTP/1.0For more information about MIME encoding as it is related to Internet mail, visit the following RFC Web site:
RFC 2068: Hypertext Transfer Protocol -- HTTP/1.1
Note Chunked transfer encoding is defined in section 3.6.
RFC 822: Standard for the Format of ARAP Internet Text Messages
Article ID: 278998 - Last Review: December 3, 2007 - Revision: 6.6