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/p3-payload.xml

    r697 r698  
    983983  <x:anchor-alias value="media-range"/>
    984984<t>
    985    The "Accept" request-header field can be used to specify certain media
    986    types which are acceptable for the response. Accept headers can be
    987    used to indicate that the request is specifically limited to a small
    988    set of desired types, as in the case of a request for an in-line
    989    image.
     985   The "Accept" request-header field can be used by user agents to specify
     986   response media types that are acceptable. Accept headers can be used to
     987   indicate that the request is specifically limited to a small set of desired
     988   types, as in the case of a request for an in-line image.
    990989</t>
    991990<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Accept"/><iref primary="true" item="Grammar" subitem="Accept-v"/><iref primary="true" item="Grammar" subitem="media-range"/><iref primary="true" item="Grammar" subitem="accept-params"/><iref primary="true" item="Grammar" subitem="accept-ext"/>
     
    11101109  <x:anchor-alias value="Accept-Charset-v"/>
    11111110<t>
    1112    The "Accept-Charset" request-header field can be used to indicate what
    1113    character sets are acceptable for the response. This field allows
     1111   The "Accept-Charset" request-header field can be used by user agents to
     1112   indicate what response character sets are acceptable. This field allows
    11141113   clients capable of understanding more comprehensive or special-purpose
    1115    character sets to signal that capability to a server which is
    1116    capable of representing documents in those character sets.
     1114   character sets to signal that capability to a server which is capable of
     1115   representing documents in those character sets.
    11171116</t>
    11181117<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Accept-Charset"/><iref primary="true" item="Grammar" subitem="Accept-Charset-v"/>
     
    11551154  <x:anchor-alias value="codings"/>
    11561155<t>
    1157    The "Accept-Encoding" request-header field is similar to Accept, but
    1158    restricts the content-codings (<xref target="content.codings"/>) that are acceptable in
    1159    the response.
     1156   The "Accept-Encoding" request-header field can be used by user agents to
     1157   indicate what response content-codings (<xref target="content.codings"/>)
     1158   are acceptable in the response.
    11601159</t>
    11611160<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Accept-Encoding"/><iref primary="true" item="Grammar" subitem="Accept-Encoding-v"/><iref primary="true" item="Grammar" subitem="codings"/>
     
    12451244  <x:anchor-alias value="language-range"/>
    12461245<t>
    1247    The "Accept-Language" request-header field is similar to Accept, but
    1248    restricts the set of natural languages that are preferred as a
    1249    response to the request. Language tags are defined in <xref target="language.tags"/>.
     1246   The "Accept-Language" request-header field can be used by user agents to
     1247   indicate the set of natural languages that are preferred in the response.
     1248   Language tags are defined in <xref target="language.tags"/>.
    12501249</t>
    12511250<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Accept-Language"/><iref primary="true" item="Grammar" subitem="Accept-Language-v"/><iref primary="true" item="Grammar" subitem="language-range"/>
     
    13411340  <x:anchor-alias value="Content-Encoding-v"/>
    13421341<t>
    1343    The "Content-Encoding" entity-header field is used as a modifier to the
    1344    media-type. When present, its value indicates what additional content
    1345    codings have been applied to the entity-body, and thus what decoding
    1346    mechanisms must be applied in order to obtain the media-type
    1347    referenced by the Content-Type header field. Content-Encoding is
    1348    primarily used to allow a document to be compressed without losing
    1349    the identity of its underlying media type.
     1342   The "Content-Encoding" entity-header field indicates what content-codings
     1343   have been applied to the entity-body, and thus what decoding mechanisms
     1344   must be applied in order to obtain the media-type referenced by the
     1345   Content-Type header field. Content-Encoding is primarily used to allow a
     1346   document to be compressed without losing the identity of its underlying
     1347   media type.
    13501348</t>
    13511349<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Content-Encoding"/><iref primary="true" item="Grammar" subitem="Content-Encoding-v"/>
     
    13921390<t>
    13931391   The "Content-Language" entity-header field describes the natural
    1394    language(s) of the intended audience for the enclosed entity. Note
    1395    that this might not be equivalent to all the languages used within
    1396    the entity-body.
     1392   language(s) of the intended audience for the entity. Note that this might
     1393   not be equivalent to all the languages used within the entity-body.
    13971394</t>
    13981395<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Content-Language"/><iref primary="true" item="Grammar" subitem="Content-Language-v"/>
     
    14451442  <x:anchor-alias value="Content-Location-v"/>
    14461443<t>
    1447    The "Content-Location" entity-header field &MAY; be used to supply the
    1448    resource location for the entity enclosed in the message when that
    1449    entity is accessible from a location separate from the requested
    1450    resource's URI. A server &SHOULD; provide a Content-Location for the
    1451    variant corresponding to the response entity; especially in the case
    1452    where a resource has multiple entities associated with it, and those
    1453    entities actually have separate locations by which they might be
    1454    individually accessed, the server &SHOULD; provide a Content-Location
    1455    for the particular variant which is returned.
     1444   The "Content-Location" entity-header field is used to supply a URI for the
     1445   entity in the message when it is accessible from a location separate from
     1446   the requested resource's URI.
     1447</t>
     1448<t>
     1449   A server &SHOULD; provide a Content-Location for the variant corresponding
     1450   to the response entity, especially in the case where a resource has multiple
     1451   entities associated with it, and those entities actually have separate
     1452   locations by which they might be individually accessed, the server &SHOULD;
     1453   provide a Content-Location for the particular variant which is returned.
    14561454</t>
    14571455<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Content-Location"/><iref primary="true" item="Grammar" subitem="Content-Location-v"/>
     
    15741572<t>
    15751573   The "Content-Type" entity-header field indicates the media type of the
    1576    entity-body sent to the recipient or, in the case of the HEAD method,
    1577    the media type that would have been sent had the request been a GET.
     1574   entity-body. In the case of responses to the HEAD method, the media type is
     1575   that which would have been sent had the request been a GET.
    15781576</t>
    15791577<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Content-Type"/><iref primary="true" item="Grammar" subitem="Content-Type-v"/>
Note: See TracChangeset for help on using the changeset viewer.