Changeset 1944 for draft-ietf-httpbis/latest/p5-range.xml
- Timestamp:
- 22/10/12 15:34:30 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p5-range.xml
r1929 r1944 393 393 header fields consist of the most recent 200 response's header fields. 394 394 If all of the matching stored responses are 206 responses, then the 395 stored response with the most header fields is used as the source of395 stored response with the most recent header fields is used as the source of 396 396 header fields for the combined response, except that the client &MUST; 397 397 use other header fields provided in the new response, aside from … … 510 510 <t> 511 511 In the case of a byte range request: 512 Aserver sending a response with status code <x:ref>416 (Requested Range Not512 a server sending a response with status code <x:ref>416 (Requested Range Not 513 513 Satisfiable)</x:ref> &SHOULD; include a Content-Range field with a byte-range-resp-spec 514 514 of "*". The instance-length specifies the current length of
Note: See TracChangeset
for help on using the changeset viewer.