Ignore:
Timestamp:
Sep 26, 2009, 3:09:09 AM (10 years ago)
Author:
julian.reschke@…
Message:

editorial: enhance readability of header introductions

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p5-range.xml

    r697 r698  
    458458  <x:anchor-alias value="acceptable-ranges"/>
    459459<t>
    460    The "Accept-Ranges" response-header field allows the server to
    461    indicate its acceptance of range requests for a resource:
     460   The "Accept-Ranges" response-header field allows a resource to indicate
     461   its acceptance of range requests.
    462462</t>
    463463<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"/>
     
    807807  <x:anchor-alias value="other-range-set"/>
    808808<t>
    809    HTTP retrieval requests using conditional or unconditional GET
    810    methods &MAY; request one or more sub-ranges of the entity, instead of
    811    the entire entity, using the Range request header, which applies to
    812    the entity returned as the result of the request:
     809   The "Range" request-header field defines the GET method (conditional or
     810   not) to request one or more sub-ranges of the response entity-body, instead
     811   of the entire entity body.
    813812</t>
    814813<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Range"/>
Note: See TracChangeset for help on using the changeset viewer.