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

Timestamp:

26/09/09 10:09:09 (13 years ago)

Author:

julian.reschke@…

Message:

editorial: enhance readability of header introductions

File:

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

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

@@ -1871 +1871 @@
    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.
+   associated with the resource.
 </t>
 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Allow"/><iref primary="true" item="Grammar" subitem="Allow-v"/>
@@ -2006 +2005 @@
   <x:anchor-alias value="Location-v"/>
 <t>
-   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)
-   responses, the Location is that of the new resource which was created
-   by the request. For 3xx responses, the location &SHOULD; indicate the
-   server's preferred URI for automatic redirection to the resource. The
-   field value consists of a single URI.
+   The "Location" response-header field is used to identify a newly created
+   resource, or to redirect the recipient to a different location for
+   completion of the request.
+</t>
+<t>
+   For 201 (Created) responses, the Location is the URI of the new resource
+   which was created by the request. For 3xx responses, the location &SHOULD;
+   indicate the server's preferred URI for automatic redirection to the
+   resource.
+</t>
+<t>
+   The field value consists of a single URI.
 </t>
 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Location"/><iref primary="true" item="Grammar" subitem="Location-v"/>
@@ -2049 +2053 @@
 <t>
    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
-   next inbound server. This can be useful when the client is attempting
-   to trace a request chain which appears to be failing or looping in
-   mid-chain.
+   TRACE (<xref target="TRACE"/>) and OPTIONS (<xref target="OPTIONS"/>)
+   methods to limit the number of times that the request is forwarded by
+   proxies or gateways. This can be useful when the client is attempting to
+   trace a request which appears to be failing or looping in mid-chain.
 </t>
 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Max-Forwards"/><iref primary="true" item="Grammar" subitem="Max-Forwards-v"/>
@@ -2085 +2088 @@
   <x:anchor-alias value="Referer-v"/>
 <t>
-   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
-   misspelled.).
+   The "Referer" [sic] request-header field allows the client to specify the
+   URI of the resource from which the request-target was obtained (the
+   "referrer", although the header field is misspelled.).
 </t>
 <t>
@@ -2131 +2133 @@
    be unavailable to the requesting client. This field &MAY; also be used
    with any 3xx (Redirection) response to indicate the minimum time the
-   user-agent is asked wait before issuing the redirected request. The
-   value of this field can be either an HTTP-date or an integer number
+   user-agent is asked wait before issuing the redirected request.
+</t>
+<t>
+   The value of this field can be either an HTTP-date or an integer number
    of seconds (in decimal) after the time of the response.
 </t>
@@ -2166 +2170 @@
 <t>
    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
-   identifying the server and any significant subproducts. The product
-   tokens are listed in order of their significance for identifying the
-   application.
+   software used by the origin server to handle the request.
+</t>
+<t>
+   The field can contain multiple product tokens (&product-tokens;) and
+   comments (&header-fields;) identifying the server and any significant
+   subproducts. The product tokens are listed in order of their significance
+   for identifying the application.
 </t>
 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Server"/><iref primary="true" item="Grammar" subitem="Server-v"/>
@@ -2209 +2215 @@
    the tracing of protocol violations, and automated recognition of user
    agents for the sake of tailoring responses to avoid particular user
-   agent limitations. User agents &SHOULD; include this field with
-   requests. The field can contain multiple product tokens (&product-tokens;)
-   and comments identifying the agent and any subproducts which form a
-   significant part of the user agent. By convention, the product tokens
-   are listed in order of their significance for identifying the
-   application.
+   agent limitations.
+</t>
+<t>
+   User agents &SHOULD; include this field with requests. The field can contain
+   multiple product tokens (&product-tokens;) and comments (&header-fields;)
+   identifying the agent and any subproducts which form a significant part of
+   the user agent. By convention, the product tokens are listed in order of
+   their significance for identifying the application.
 </t>
 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="User-Agent"/><iref primary="true" item="Grammar" subitem="User-Agent-v"/>