Ignore:
Timestamp:
Mar 10, 2011, 10:45:30 PM (9 years ago)
Author:
fielding@…
Message:

Remove header field classifications.

Addresses #224 and #104

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r1161 r1163  
    246246   that defines the protocol referred to as "HTTP/1.1" and, taken together,
    247247   obsoletes RFC 2616.  Part 2 defines the semantics of HTTP messages
    248    as expressed by request methods, request-header fields, response status codes,
    249    and response-header fields.
     248   as expressed by request methods, request header fields, response status codes,
     249   and response header fields.
    250250</t>
    251251</abstract>
     
    282282   In particular, the sections will be ordered according to the typical
    283283   processing of an HTTP request message (after message parsing): resource
    284    mapping, general header fields, methods, request modifiers, response
    285    status, and resource metadata.  The current mess reflects how widely
    286    dispersed these topics and associated requirements had become in
    287    <xref target="RFC2616"/>.
     284   mapping, methods, request modifying header fields, response status,
     285   status modifying header fields, and resource metadata.  The current mess
     286   reflects how widely dispersed these topics and associated requirements
     287   had become in <xref target="RFC2616"/>.
    288288</t>
    289289
     
    530530  <x:anchor-alias value="request-header"/>
    531531<t>
    532    The request-header fields allow the client to pass additional
     532   The request header fields allow the client to pass additional
    533533   information about the request, and about the client itself, to the
    534534   server. These fields act as request modifiers, with semantics
     
    560560  <c>User-Agent</c> <c><xref target="header.user-agent"/></c>
    561561</texttable>
    562 <t>
    563    Request-header field names can be extended reliably only in
    564    combination with a change in the protocol version. However, new or
    565    experimental header fields &MAY; be given the semantics of request-header
    566    fields if all parties in the communication recognize them to
    567    be request-header fields.
    568 </t>
    569562</section>
    570563
     
    723716  <x:anchor-alias value="response-header"/>
    724717<t>
    725    The response-header fields allow the server to pass additional
     718   The response header fields allow the server to pass additional
    726719   information about the response which cannot be placed in the Status-Line.
    727720   These header fields give information about the server and about
     
    729722</t>
    730723<texttable align="left">
    731   <ttcol>Method Name</ttcol><ttcol>Defined in...</ttcol>
     724  <ttcol>Header Field Name</ttcol><ttcol>Defined in...</ttcol>
    732725
    733726  <c>Accept-Ranges</c> <c>&header-accept-ranges;</c>
     
    742735  <c>WWW-Authenticate</c> <c>&header-www-authenticate;</c>
    743736</texttable>
    744 <t>
    745    Response-header field names can be extended reliably only in
    746    combination with a change in the protocol version. However, new or
    747    experimental header fields &MAY; be given the semantics of response-header
    748    fields if all parties in the communication recognize them to
    749    be response-header fields.
    750 </t>
    751737</section>
    752738
     
    911897</t>
    912898<t>
    913    The Max-Forwards request-header field &MAY; be used to target a
     899   The Max-Forwards header field &MAY; be used to target a
    914900   specific proxy in the request chain (see <xref target="header.max-forwards"/>).
    915901   If no Max-Forwards field is present in the request, then the forwarded
     
    19671953  </rdf:Description>
    19681954<t>
    1969    The precondition given in one or more of the request-header fields
     1955   The precondition given in one or more of the header fields
    19701956   evaluated to false when it was tested on the server, as defined in
    19711957   &status-412;.
     
    20222008  </rdf:Description>
    20232009<t>
    2024    The request included a Range request-header field (&header-range;) and none of
     2010   The request included a Range header field (&header-range;) and none of
    20252011   the range-specifier values in this field overlap the current extent
    20262012   of the selected resource. See &status-416;.
     
    20322018  <iref primary="true" item="Status Codes" subitem="417 Expectation Failed" x:for-anchor=""/>
    20332019<t>
    2034    The expectation given in an Expect request-header field (see <xref target="header.expect"/>)
     2020   The expectation given in an Expect header field (see <xref target="header.expect"/>)
    20352021   could not be met by this server, or, if the server is a proxy,
    20362022   the server has unambiguous evidence that the request could not be met
     
    21712157  <x:anchor-alias value="Allow-v"/>
    21722158<t>
    2173    The "Allow" response-header field lists the set of methods advertised as
     2159   The "Allow" header field lists the set of methods advertised as
    21742160   supported by the target resource. The purpose of this field is strictly to
    21752161   inform the recipient of valid request methods associated with the resource.
     
    22052191  <x:anchor-alias value="expect-params"/>
    22062192<t>
    2207    The "Expect" request-header field is used to indicate that particular
     2193   The "Expect" header field is used to indicate that particular
    22082194   server behaviors are required by the client.
    22092195</t>
     
    22402226   return a 417 (Expectation Failed) status code if it receives a request
    22412227   with an expectation that it cannot meet. However, the Expect
    2242    request-header field itself is end-to-end; it &MUST; be forwarded if the
     2228   header field itself is end-to-end; it &MUST; be forwarded if the
    22432229   request is forwarded.
    22442230</t>
     
    22592245  <x:anchor-alias value="mailbox"/>
    22602246<t>
    2261    The "From" request-header field, if given, &SHOULD; contain an Internet
     2247   The "From" header field, if given, &SHOULD; contain an Internet
    22622248   e-mail address for the human user who controls the requesting user
    22632249   agent. The address &SHOULD; be machine-usable, as defined by "mailbox"
     
    23072293  <x:anchor-alias value="Location-v"/>
    23082294<t>
    2309    The "Location" response-header field is used to identify a newly created
     2295   The "Location" header field is used to identify a newly created
    23102296   resource, or to redirect the recipient to a different location for
    23112297   completion of the request.
     
    23692355  <x:anchor-alias value="Max-Forwards-v"/>
    23702356<t>
    2371    The "Max-Forwards" request-header field provides a mechanism with the
     2357   The "Max-Forwards" header field provides a mechanism with the
    23722358   TRACE (<xref target="TRACE"/>) and OPTIONS (<xref target="OPTIONS"/>)
    23732359   methods to limit the number of times that the request is forwarded by
     
    24042390  <x:anchor-alias value="Referer-v"/>
    24052391<t>
    2406    The "Referer" [sic] request-header field allows the client to specify the
     2392   The "Referer" [sic] header field allows the client to specify the
    24072393   URI of the resource from which the effective request URI was obtained (the
    24082394   "referrer", although the header field is misspelled.).
     
    24452431  <x:anchor-alias value="Retry-After-v"/>
    24462432<t>
    2447    The response-header "Retry-After" field can be used with a 503 (Service
     2433   The header "Retry-After" field can be used with a 503 (Service
    24482434   Unavailable) response to indicate how long the service is expected to
    24492435   be unavailable to the requesting client. This field &MAY; also be used
     
    24852471  <x:anchor-alias value="Server-v"/>
    24862472<t>
    2487    The "Server" response-header field contains information about the
     2473   The "Server" header field contains information about the
    24882474   software used by the origin server to handle the request.
    24892475</t>
     
    25072493<t>
    25082494   If the response is being forwarded through a proxy, the proxy
    2509    application &MUST-NOT; modify the Server response-header field. Instead, it
     2495   application &MUST-NOT; modify the Server header field. Instead, it
    25102496   &MUST; include a Via field (as described in &header-via;).
    25112497</t>
     
    25272513  <x:anchor-alias value="User-Agent-v"/>
    25282514<t>
    2529    The "User-Agent" request-header field contains information about the user
     2515   The "User-Agent" header field contains information about the user
    25302516   agent originating the request. User agents &SHOULD; include this field with
    25312517   requests.
Note: See TracChangeset for help on using the changeset viewer.