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/p2-semantics.xml

    r695 r697  
    18681868  <x:anchor-alias value="Allow-v"/>
    18691869<t>
    1870       The response-header field "Allow" lists the set of methods advertised as
    1871       supported by the resource identified by the request-target. The purpose of
    1872       this field is strictly to inform the recipient of valid methods
    1873       associated with the resource. An Allow header field &MUST; be
    1874       present in a 405 (Method Not Allowed) response.
     1870   The "Allow" response-header field lists the set of methods advertised as
     1871   supported by the resource identified by the request-target. The purpose of
     1872   this field is strictly to inform the recipient of valid methods
     1873   associated with the resource. An Allow header field &MUST; be
     1874   present in a 405 (Method Not Allowed) response.
    18751875</t>
    18761876<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Allow"/><iref primary="true" item="Grammar" subitem="Allow-v"/>
     
    19041904  <x:anchor-alias value="expect-params"/>
    19051905<t>
    1906    The request-header field "Expect" is used to indicate that particular
     1906   The "Expect" request-header field is used to indicate that particular
    19071907   server behaviors are required by the client.
    19081908</t>
     
    19581958  <x:anchor-alias value="mailbox"/>
    19591959<t>
    1960    The request-header field "From", if given, &SHOULD; contain an Internet
     1960   The "From" request-header field, if given, &SHOULD; contain an Internet
    19611961   e-mail address for the human user who controls the requesting user
    19621962   agent. The address &SHOULD; be machine-usable, as defined by "mailbox"
     
    20062006  <x:anchor-alias value="Location-v"/>
    20072007<t>
    2008    The response-header field "Location" is used for the identification of a
     2008   The "Location" response-header field is used for the identification of a
    20092009   new resource or to redirect the recipient to a location other than the
    20102010   request-target for completion of the request.  For 201 (Created)
     
    20482048  <x:anchor-alias value="Max-Forwards-v"/>
    20492049<t>
    2050    The request-header "Max-Forwards" field provides a mechanism with the
     2050   The "Max-Forwards" request-header field provides a mechanism with the
    20512051   TRACE (<xref target="TRACE"/>) and OPTIONS (<xref target="OPTIONS"/>) methods to limit the
    20522052   number of proxies or gateways that can forward the request to the
     
    20852085  <x:anchor-alias value="Referer-v"/>
    20862086<t>
    2087    The request-header field "Referer" [sic] allows the client to specify, for
     2087   The "Referer" [sic] request-header field allows the client to specify, for
    20882088   the server's benefit, the address (URI) of the resource from which the
    20892089   request-target was obtained (the "referrer", although the header field is
     
    21652165  <x:anchor-alias value="Server-v"/>
    21662166<t>
    2167    The response-header field "Server" contains information about the
     2167   The "Server" response-header field contains information about the
    21682168   software used by the origin server to handle the request. The field
    21692169   can contain multiple product tokens (&product-tokens;) and comments
     
    22052205  <x:anchor-alias value="User-Agent-v"/>
    22062206<t>
    2207    The request-header field "User-Agent" contains information about the
     2207   The "User-Agent" request-header field contains information about the
    22082208   user agent originating the request. This is for statistical purposes,
    22092209   the tracing of protocol violations, and automated recognition of user
Note: See TracChangeset for help on using the changeset viewer.