206 Patial Content

http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html


10.2.7 206 Partial Content

The server has fulfilled the partial GET request for the resource. The request MUST have included a Range header field (section 14.35) indicating the desired range, and MAY have included an If-Range header field (section 14.27) to make the request conditional.

서버측은 리소스의 부분적인 GET 요청에 대해 수행되어져야 한다. 요청은 반드시 바라는 범위를 나타내는 Range 헤더필드를 포함해야한다. 그리고 조건부 요청을 만드는 If-Range 헤더 필드를 포함하여도 무방하다.

( 응답헤더 예제)

HTTP/1.1 206 Partial Content
Server: apache
Date: Tue, 07 Dec 2010 03:50:20 GMT
Content-Type: text/plain
Connection: keep-alive
P3P: CP='NOI CURa ADMa DEVa TAIa OUR DELa BUS IND PHY ONL UNI COM NAV INT DEM PRE'
Last-Modified: Tue, 29 Jun 2010 01:15:33 GMT
ETag: "15800fd-470452-4c294935"
Accept-Ranges: bytes
Content-Length: 4653137
Content-Range: bytes 1025-4654161/4654162

The response MUST include the following header fields:
응답은 반드시 아래의 헤더필드들을 포함하여야 한다.

      - Either a Content-Range header field (section 14.16) indicating
        the range included with this response, or a multipart/byteranges
        Content-Type including Content-Range fields for each part. If a
        Content-Length header field is present in the response, its
        value MUST match the actual number of OCTETs transmitted in the
        message-body.
	응답을 포함한 범위를 나타내는 Content-Range 필드나, 각 부분을 위한 Content-Range 필드를 
	포함한 multipart/byterange Content-Type 필드.
	만약 Content-Length 필드가 응답에 표현되었다면 그것은 message-body안에 전송된
	실제 바이트의 수와 일치되어져야 한다.

      - Date
	날짜

      - ETag and/or Content-Location, if the header would have been sent
        in a 200 response to the same request
	만약 같은 요청에 대한 200 응답코드안에 보내진다면, ETag 혹은 Content-Location를 
	포함하여야한다.

      - Expires, Cache-Control, and/or Vary, if the field-value might
        differ from that sent in any previous response for the same
        variant

If the 206 response is the result of an If-Range request that used a strong cache validator (see section 13.3.3), the response SHOULD NOT include other entity-headers. If the response is the result of an If-Range request that used a weak validator, the response MUST NOT include other entity-headers; this prevents inconsistencies between cached entity-bodies and updated headers. Otherwise, the response MUST include all of the entity-headers that would have been returned with a 200 (OK) response to the same request.

A cache MUST NOT combine a 206 response with other previously cached content if the ETag or Last-Modified headers do not match exactly, see 13.5.4.

A cache that does not support the Range and Content-Range headers MUST NOT cache 206 (Partial) responses.