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

    r697 r698  
    18711871   supported by the resource identified by the request-target. The purpose of
    18721872   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.
     1873   associated with the resource.
    18751874</t>
    18761875<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Allow"/><iref primary="true" item="Grammar" subitem="Allow-v"/>
     
    20062005  <x:anchor-alias value="Location-v"/>
    20072006<t>
    2008    The "Location" response-header field is used for the identification of a
    2009    new resource or to redirect the recipient to a location other than the
    2010    request-target for completion of the request.  For 201 (Created)
    2011    responses, the Location is that of the new resource which was created
    2012    by the request. For 3xx responses, the location &SHOULD; indicate the
    2013    server's preferred URI for automatic redirection to the resource. The
    2014    field value consists of a single URI.
     2007   The "Location" response-header field is used to identify a newly created
     2008   resource, or to redirect the recipient to a different location for
     2009   completion of the request.
     2010</t>
     2011<t>
     2012   For 201 (Created) responses, the Location is the URI of the new resource
     2013   which was created by the request. For 3xx responses, the location &SHOULD;
     2014   indicate the server's preferred URI for automatic redirection to the
     2015   resource.
     2016</t>
     2017<t>
     2018   The field value consists of a single URI.
    20152019</t>
    20162020<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Location"/><iref primary="true" item="Grammar" subitem="Location-v"/>
     
    20492053<t>
    20502054   The "Max-Forwards" request-header field provides a mechanism with the
    2051    TRACE (<xref target="TRACE"/>) and OPTIONS (<xref target="OPTIONS"/>) methods to limit the
    2052    number of proxies or gateways that can forward the request to the
    2053    next inbound server. This can be useful when the client is attempting
    2054    to trace a request chain which appears to be failing or looping in
    2055    mid-chain.
     2055   TRACE (<xref target="TRACE"/>) and OPTIONS (<xref target="OPTIONS"/>)
     2056   methods to limit the number of times that the request is forwarded by
     2057   proxies or gateways. This can be useful when the client is attempting to
     2058   trace a request which appears to be failing or looping in mid-chain.
    20562059</t>
    20572060<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Max-Forwards"/><iref primary="true" item="Grammar" subitem="Max-Forwards-v"/>
     
    20852088  <x:anchor-alias value="Referer-v"/>
    20862089<t>
    2087    The "Referer" [sic] request-header field allows the client to specify, for
    2088    the server's benefit, the address (URI) of the resource from which the
    2089    request-target was obtained (the "referrer", although the header field is
    2090    misspelled.).
     2090   The "Referer" [sic] request-header field allows the client to specify the
     2091   URI of the resource from which the request-target was obtained (the
     2092   "referrer", although the header field is misspelled.).
    20912093</t>
    20922094<t>
     
    21312133   be unavailable to the requesting client. This field &MAY; also be used
    21322134   with any 3xx (Redirection) response to indicate the minimum time the
    2133    user-agent is asked wait before issuing the redirected request. The
    2134    value of this field can be either an HTTP-date or an integer number
     2135   user-agent is asked wait before issuing the redirected request.
     2136</t>
     2137<t>
     2138   The value of this field can be either an HTTP-date or an integer number
    21352139   of seconds (in decimal) after the time of the response.
    21362140</t>
     
    21662170<t>
    21672171   The "Server" response-header field contains information about the
    2168    software used by the origin server to handle the request. The field
    2169    can contain multiple product tokens (&product-tokens;) and comments
    2170    identifying the server and any significant subproducts. The product
    2171    tokens are listed in order of their significance for identifying the
    2172    application.
     2172   software used by the origin server to handle the request.
     2173</t>
     2174<t>
     2175   The field can contain multiple product tokens (&product-tokens;) and
     2176   comments (&header-fields;) identifying the server and any significant
     2177   subproducts. The product tokens are listed in order of their significance
     2178   for identifying the application.
    21732179</t>
    21742180<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Server"/><iref primary="true" item="Grammar" subitem="Server-v"/>
     
    22092215   the tracing of protocol violations, and automated recognition of user
    22102216   agents for the sake of tailoring responses to avoid particular user
    2211    agent limitations. User agents &SHOULD; include this field with
    2212    requests. The field can contain multiple product tokens (&product-tokens;)
    2213    and comments identifying the agent and any subproducts which form a
    2214    significant part of the user agent. By convention, the product tokens
    2215    are listed in order of their significance for identifying the
    2216    application.
     2217   agent limitations.
     2218</t>
     2219<t>
     2220   User agents &SHOULD; include this field with requests. The field can contain
     2221   multiple product tokens (&product-tokens;) and comments (&header-fields;)
     2222   identifying the agent and any subproducts which form a significant part of
     2223   the user agent. By convention, the product tokens are listed in order of
     2224   their significance for identifying the application.
    22172225</t>
    22182226<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="User-Agent"/><iref primary="true" item="Grammar" subitem="User-Agent-v"/>
Note: See TracChangeset for help on using the changeset viewer.