206 Partial Content

[Tyler Durrant]

I know this is not the place to find this, but i was hoping some one in here could point me in the right direction. I am using fiddler to watch a web response and it gives me a 206, the problem is it times out. I am trying to find the correct formatting for a chunked response preferably with an example

HTTP/1.1 206 Partial Content

Content-Type: audio/mpeg

Content-Length: 1842619

Content-Length: 1842619

Content-Range: bytes 0-1842618/1842619

Accept-Ranges: bytes

Date: Mon, 26 Aug 2013 18:48:24 GMT

Server: CherryPy/3.1.2 WSGI Server

this is what is getting sent back, which i know is not right, but I am having a problem figuring out what is wrong. All I am looking for is a link in the right direction. I have check w3.org and looked it up on google biut all i get is the same thing. "206 is a partial content response", no example no these parts are mandatory, etc etc

[EricLaw]

I'm not sure I understand the question; I think you're confused about what a "chunked response" is.

 

A HTTP Chunked Response (see RFC2616) does not contain a Content-Length response header; it instead sends the response body in multiple blocks, each preceded by a chunk length value in Hex. To see an example of this, simply click any plaintext HTTP response in Fiddler that has a body, click the Inspectors tab, click the Transformer response inspector, and check the Chunked Transfer Encoding box at the top. Then click over to the Raw inspector and see what happened to the body.

 

In contrast, a HTTP/206 response is a partial response that only contains a portion of the response body. These responses are sent when the client sends a Range header indicating which portion of the response it wants; these ranged-requests are usually sent when the client already has part of a file locally and wants to retrieve the rest of it. The response body doesn't have any special format; only the Content-Range header tells the client which portion of the response was returned.