Changeset 697 for draft-ietf-httpbis/latest/p5-range.xml
- Timestamp:
- Sep 25, 2009, 7:43:16 AM (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p5-range.xml
r689 r697 458 458 <x:anchor-alias value="acceptable-ranges"/> 459 459 <t> 460 The response-header "Accept-Ranges"field allows the server to461 460 The "Accept-Ranges" response-header field allows the server to 461 indicate its acceptance of range requests for a resource: 462 462 </t> 463 463 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Accept-Ranges"/><iref primary="true" item="Grammar" subitem="Accept-Ranges-v"/><iref primary="true" item="Grammar" subitem="acceptable-ranges"/> … … 501 501 <x:anchor-alias value="other-range-resp-spec"/> 502 502 <t> 503 The entity-header "Content-Range"is sent with a partial entity-body to503 The "Content-Range" entity-header field is sent with a partial entity-body to 504 504 specify where in the full entity-body the partial body should be 505 505 applied. Range units are defined in <xref target="range.units"/>. … … 655 655 </t> 656 656 <t> 657 The request header "If-Range"allows a client to "short-circuit" the second657 The "If-Range" request-header field allows a client to "short-circuit" the second 658 658 request. Informally, its meaning is `if the entity is unchanged, send 659 659 me the part(s) that I am missing; otherwise, send me the entire new
Note: See TracChangeset
for help on using the changeset viewer.