Changeset 363 for draft-ietf-httpbis/latest/p5-range.xml
- Timestamp:
- 13/11/08 18:01:19 (14 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p5-range.xml
r359 r363 255 255 <x:anchor-alias value="SP"/> 256 256 <x:anchor-alias value="token"/> 257 <x:anchor-alias value="BWS"/> 258 <x:anchor-alias value="OWS"/> 259 <x:anchor-alias value="RWS"/> 257 260 <t> 258 261 This specification uses the ABNF syntax defined in ¬ation-abnf; and … … 267 270 <figure><artwork type="abnf2616"> 268 271 <x:ref>token</x:ref> = <token, defined in &basic-rules;> 272 <x:ref>BWS</x:ref> = <BWS, defined in &basic-rules;> 273 <x:ref>OWS</x:ref> = <OWS, defined in &basic-rules;> 274 <x:ref>RWS</x:ref> = <RWS, defined in &basic-rules;> 269 275 </artwork></figure> 270 276 <t anchor="abnf.dependencies"> … … 422 428 <iref primary="true" item="Headers" subitem="Accept-Ranges" x:for-anchor=""/> 423 429 <x:anchor-alias value="Accept-Ranges"/> 430 <x:anchor-alias value="Accept-Ranges-v"/> 424 431 <x:anchor-alias value="acceptable-ranges"/> 425 432 <t> 426 The Accept-Ranges response-headerfield allows the server to433 The response-header "Accept-Ranges" field allows the server to 427 434 indicate its acceptance of range requests for a resource: 428 435 </t> 429 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Accept-Ranges"/><iref primary="true" item="Grammar" subitem="acceptable-ranges"/> 430 <x:ref>Accept-Ranges</x:ref> = "Accept-Ranges" ":" <x:ref>acceptable-ranges</x:ref> 436 <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"/> 437 <x:ref>Accept-Ranges</x:ref> = "Accept-Ranges" <x:ref>BWS</x:ref> ":" <x:ref>OWS</x:ref> <x:ref>Accept-Ranges-v</x:ref> 438 <x:ref>Accept-Ranges-v</x:ref> = <x:ref>acceptable-ranges</x:ref> 431 439 <x:ref>acceptable-ranges</x:ref> = 1#<x:ref>range-unit</x:ref> / "none" 432 440 </artwork></figure> … … 435 443 </t> 436 444 <figure><artwork type="example"> 437 445 Accept-Ranges: bytes 438 446 </artwork></figure> 439 447 <t> … … 447 455 </t> 448 456 <figure><artwork type="example"> 449 457 Accept-Ranges: none 450 458 </artwork></figure> 451 459 <t> … … 460 468 <x:anchor-alias value="byte-range-resp-spec"/> 461 469 <x:anchor-alias value="Content-Range"/> 470 <x:anchor-alias value="Content-Range-v"/> 462 471 <x:anchor-alias value="content-range-spec"/> 463 472 <x:anchor-alias value="instance-length"/> 464 473 <t> 465 The Content-Range entity-headeris sent with a partial entity-body to474 The entity-header "Content-Range" is sent with a partial entity-body to 466 475 specify where in the full entity-body the partial body should be 467 476 applied. Range units are defined in <xref target="range.units"/>. 468 477 </t> 469 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Content-Range"/><iref primary="true" item="Grammar" subitem="content-range-spec"/><iref primary="true" item="Grammar" subitem="byte-content-range-spec"/><iref primary="true" item="Grammar" subitem="byte-range-resp-spec"/><iref primary="true" item="Grammar" subitem="instance-length"/> 470 <x:ref>Content-Range</x:ref> = "Content-Range" ":" <x:ref>content-range-spec</x:ref> 478 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Content-Range"/><iref primary="true" item="Grammar" subitem="Content-Range-v"/><iref primary="true" item="Grammar" subitem="content-range-spec"/><iref primary="true" item="Grammar" subitem="byte-content-range-spec"/><iref primary="true" item="Grammar" subitem="byte-range-resp-spec"/><iref primary="true" item="Grammar" subitem="instance-length"/> 479 <x:ref>Content-Range</x:ref> = "Content-Range" <x:ref>BWS</x:ref> ":" <x:ref>OWS</x:ref> <x:ref>Content-Range-v</x:ref> 480 <x:ref>Content-Range-v</x:ref> = <x:ref>content-range-spec</x:ref> 471 481 472 482 <x:ref>content-range-spec</x:ref> = <x:ref>byte-content-range-spec</x:ref> … … 544 554 </t> 545 555 <figure><artwork type="example"> 546 547 548 549 550 551 556 HTTP/1.1 206 Partial Content 557 Date: Wed, 15 Nov 1995 06:25:24 GMT 558 Last-Modified: Wed, 15 Nov 1995 04:58:08 GMT 559 Content-Range: bytes 21010-47021/47022 560 Content-Length: 26012 561 Content-Type: image/gif 552 562 </artwork></figure> 553 563 <t> … … 597 607 <iref primary="true" item="Headers" subitem="If-Range" x:for-anchor=""/> 598 608 <x:anchor-alias value="If-Range"/> 609 <x:anchor-alias value="If-Range-v"/> 599 610 <t> 600 611 If a client has a partial copy of an entity in its cache, and wishes … … 607 618 </t> 608 619 <t> 609 The If-Range headerallows a client to "short-circuit" the second620 The request header "If-Range" allows a client to "short-circuit" the second 610 621 request. Informally, its meaning is `if the entity is unchanged, send 611 622 me the part(s) that I am missing; otherwise, send me the entire new 612 623 entity'. 613 624 </t> 614 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="If-Range"/> 615 <x:ref>If-Range</x:ref> = "If-Range" ":" ( <x:ref>entity-tag</x:ref> / <x:ref>HTTP-date</x:ref> ) 625 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="If-Range"/><iref primary="true" item="Grammar" subitem="If-Range-v"/> 626 <x:ref>If-Range</x:ref> = "If-Range" <x:ref>BWS</x:ref> ":" <x:ref>OWS</x:ref> <x:ref>If-Range-v</x:ref> 627 <x:ref>If-Range-v</x:ref> = <x:ref>entity-tag</x:ref> / <x:ref>HTTP-date</x:ref> 616 628 </artwork></figure> 617 629 <t> … … 740 752 <section title="Range Retrieval Requests" anchor="range.retrieval.requests"> 741 753 <x:anchor-alias value="Range"/> 754 <x:anchor-alias value="Range-v"/> 742 755 <t> 743 756 HTTP retrieval requests using conditional or unconditional GET … … 746 759 the entity returned as the result of the request: 747 760 </t> 748 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Range"/> 749 <x:ref>Range</x:ref> = "Range" ":" <x:ref>ranges-specifier</x:ref> 761 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Range"/><iref primary="true" item="Grammar" subitem="Range-v"/> 762 <x:ref>Range</x:ref> = "Range" <x:ref>BWS</x:ref> ":" <x:ref>OWS</x:ref> <x:ref>Range-v</x:ref> 763 <x:ref>Range-v</x:ref> = <x:ref>ranges-specifier</x:ref> 750 764 </artwork></figure> 751 765 <t> … … 1378 1392 Use "/" instead of "|" for alternatives. 1379 1393 </t> 1394 <t> 1395 Introduce new ABNF rules for "bad" whitespace ("BWS"), optional 1396 whitespace ("OWS") and required whitespace ("RWS"). 1397 </t> 1398 <t> 1399 Rewrite ABNFs to spell out whitespace rules, factor out 1400 header value format definitions. 1401 </t> 1380 1402 </list> 1381 1403 </t>
Note: See TracChangeset
for help on using the changeset viewer.