Ignore:
Timestamp:
Sep 25, 2009, 7:43:16 AM (10 years ago)
Author:
julian.reschke@…
Message:

editorial: rephrase header introductions ("the *-header field 'foobar'" -> "the "foobar" *-header field")

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p3-payload.xml

    r690 r697  
    983983  <x:anchor-alias value="media-range"/>
    984984<t>
    985    The request-header field "Accept" can be used to specify certain media
     985   The "Accept" request-header field can be used to specify certain media
    986986   types which are acceptable for the response. Accept headers can be
    987987   used to indicate that the request is specifically limited to a small
     
    11101110  <x:anchor-alias value="Accept-Charset-v"/>
    11111111<t>
    1112    The request-header field "Accept-Charset" can be used to indicate what
     1112   The "Accept-Charset" request-header field can be used to indicate what
    11131113   character sets are acceptable for the response. This field allows
    11141114   clients capable of understanding more comprehensive or special-purpose
     
    11551155  <x:anchor-alias value="codings"/>
    11561156<t>
    1157    The request-header field "Accept-Encoding" is similar to Accept, but
     1157   The "Accept-Encoding" request-header field is similar to Accept, but
    11581158   restricts the content-codings (<xref target="content.codings"/>) that are acceptable in
    11591159   the response.
     
    12451245  <x:anchor-alias value="language-range"/>
    12461246<t>
    1247    The request-header field "Accept-Language" is similar to Accept, but
     1247   The "Accept-Language" request-header field is similar to Accept, but
    12481248   restricts the set of natural languages that are preferred as a
    12491249   response to the request. Language tags are defined in <xref target="language.tags"/>.
     
    13411341  <x:anchor-alias value="Content-Encoding-v"/>
    13421342<t>
    1343    The entity-header field "Content-Encoding" is used as a modifier to the
     1343   The "Content-Encoding" entity-header field is used as a modifier to the
    13441344   media-type. When present, its value indicates what additional content
    13451345   codings have been applied to the entity-body, and thus what decoding
     
    13911391  <x:anchor-alias value="Content-Language-v"/>
    13921392<t>
    1393    The entity-header field "Content-Language" describes the natural
     1393   The "Content-Language" entity-header field describes the natural
    13941394   language(s) of the intended audience for the enclosed entity. Note
    13951395   that this might not be equivalent to all the languages used within
     
    14451445  <x:anchor-alias value="Content-Location-v"/>
    14461446<t>
    1447    The entity-header field "Content-Location" &MAY; be used to supply the
     1447   The "Content-Location" entity-header field &MAY; be used to supply the
    14481448   resource location for the entity enclosed in the message when that
    14491449   entity is accessible from a location separate from the requested
     
    14961496  <x:anchor-alias value="Content-MD5-v"/>
    14971497<t>
    1498    The entity-header field "Content-MD5", as defined in <xref target="RFC1864"/>, is
     1498   The "Content-MD5" entity-header field, as defined in <xref target="RFC1864"/>, is
    14991499   an MD5 digest of the entity-body for the purpose of providing an
    15001500   end-to-end message integrity check (MIC) of the entity-body. (Note: a
     
    15731573  <x:anchor-alias value="Content-Type-v"/>
    15741574<t>
    1575    The entity-header field "Content-Type" indicates the media type of the
     1575   The "Content-Type" entity-header field indicates the media type of the
    15761576   entity-body sent to the recipient or, in the case of the HEAD method,
    15771577   the media type that would have been sent had the request been a GET.
     
    26752675  <x:anchor-alias value="filename-parm"/>
    26762676<t>
    2677    The Content-Disposition response-header field has been proposed as a
     2677   The "Content-Disposition" response-header field has been proposed as a
    26782678   means for the origin server to suggest a default filename if the user
    26792679   requests that the content is saved to a file. This usage is derived
Note: See TracChangeset for help on using the changeset viewer.