Changeset 697 for draft-ietf-httpbis/latest/p2-semantics.xml

Timestamp:

25/09/09 14:43:16 (13 years ago)

Author:

julian.reschke@…

Message:

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

File:

• draft-ietf-httpbis/latest/p2-semantics.xml (modified) (8 diffs)

draft-ietf-httpbis/latest/p2-semantics.xml

@@ -1868 +1868 @@
   <x:anchor-alias value="Allow-v"/>
 <t>
-      The response-header field "Allow" lists the set of methods advertised as
-      supported by the resource identified by the request-target. The purpose of
-      this field is strictly to inform the recipient of valid methods
-      associated with the resource. An Allow header field &MUST; be
-      present in a 405 (Method Not Allowed) response.
+   The "Allow" response-header field lists the set of methods advertised as
+   supported by the resource identified by the request-target. The purpose of
+   this field is strictly to inform the recipient of valid methods
+   associated with the resource. An Allow header field &MUST; be
+   present in a 405 (Method Not Allowed) response.
 </t>
 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Allow"/><iref primary="true" item="Grammar" subitem="Allow-v"/>
@@ -1904 +1904 @@
   <x:anchor-alias value="expect-params"/>
 <t>
-   The request-header field "Expect" is used to indicate that particular
+   The "Expect" request-header field is used to indicate that particular
    server behaviors are required by the client.
 </t>
@@ -1958 +1958 @@
   <x:anchor-alias value="mailbox"/>
 <t>
-   The request-header field "From", if given, &SHOULD; contain an Internet
+   The "From" request-header field, if given, &SHOULD; contain an Internet
    e-mail address for the human user who controls the requesting user
    agent. The address &SHOULD; be machine-usable, as defined by "mailbox"
@@ -2006 +2006 @@
   <x:anchor-alias value="Location-v"/>
 <t>
-   The response-header field "Location" is used for the identification of a 
+   The "Location" response-header field is used for the identification of a 
    new resource or to redirect the recipient to a location other than the 
    request-target for completion of the request.  For 201 (Created)
@@ -2048 +2048 @@
   <x:anchor-alias value="Max-Forwards-v"/>
 <t>
-   The request-header "Max-Forwards" field provides a mechanism with the
+   The "Max-Forwards" request-header field provides a mechanism with the
    TRACE (<xref target="TRACE"/>) and OPTIONS (<xref target="OPTIONS"/>) methods to limit the
    number of proxies or gateways that can forward the request to the
@@ -2085 +2085 @@
   <x:anchor-alias value="Referer-v"/>
 <t>
-   The request-header field "Referer" [sic] allows the client to specify, for
+   The "Referer" [sic] request-header field allows the client to specify, for
    the server's benefit, the address (URI) of the resource from which the
    request-target was obtained (the "referrer", although the header field is
@@ -2165 +2165 @@
   <x:anchor-alias value="Server-v"/>
 <t>
-   The response-header field "Server" contains information about the
+   The "Server" response-header field contains information about the
    software used by the origin server to handle the request. The field
    can contain multiple product tokens (&product-tokens;) and comments
@@ -2205 +2205 @@
   <x:anchor-alias value="User-Agent-v"/>
 <t>
-   The request-header field "User-Agent" contains information about the
+   The "User-Agent" request-header field contains information about the
    user agent originating the request. This is for statistical purposes,
    the tracing of protocol violations, and automated recognition of user