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/p1-messaging.xml

    r1161 r1163  
    3131  <!ENTITY header-warning         "<xref target='Part6' x:rel='#header.warning' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    3232  <!ENTITY idempotent-methods     "<xref target='Part2' x:rel='#idempotent.methods' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    33   <!ENTITY request-header-fields  "<xref target='Part2' x:rel='#request.header.fields' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    34   <!ENTITY response-header-fields "<xref target='Part2' x:rel='#response.header.fields' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    3533  <!ENTITY status-codes           "<xref target='Part2' x:rel='#status.codes' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    3634  <!ENTITY status-100             "<xref target='Part2' x:rel='#status.100' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     
    517515</section>
    518516
    519 <section title="ABNF Rules defined in other Parts of the Specification" anchor="abnf.dependencies">
    520   <x:anchor-alias value="request-header"/>
    521   <x:anchor-alias value="response-header"/>
    522   <x:anchor-alias value="Cache-Control"/>
    523   <x:anchor-alias value="Pragma"/>
    524   <x:anchor-alias value="Warning"/>
    525   <x:anchor-alias value="MIME-Version"/>
    526 <t>
    527   The ABNF rules below are defined in other parts:
    528 </t>
    529 <figure><!-- Part2--><artwork type="abnf2616">
    530   <x:ref>request-header</x:ref>  = &lt;request-header, defined in &request-header-fields;&gt;
    531   <x:ref>response-header</x:ref> = &lt;response-header, defined in &response-header-fields;&gt;
    532 </artwork></figure>
    533 <figure><!-- Part3--><artwork type="abnf2616">
    534   <x:ref>MIME-Version</x:ref>    = &lt;MIME-Version, defined in &header-mime-version;&gt;
    535 </artwork></figure>
    536 <figure><!-- Part6--><artwork type="abnf2616">
    537   <x:ref>Cache-Control</x:ref>   = &lt;Cache-Control, defined in &header-pragma;&gt;
    538   <x:ref>Pragma</x:ref>          = &lt;Pragma, defined in &header-pragma;&gt;
    539   <x:ref>Warning</x:ref>         = &lt;Warning, defined in &header-warning;&gt;
    540 </artwork></figure>
    541 </section>
    542 
    543517</section>
    544518</section>
     
    10951069   are never "public" and thus are ineligible for shared caching.
    10961070   Their default is "private" and might be further constrained via use
    1097    of the Cache-Control header field.
     1071   of the Cache-Control header field (&header-cache-control;).
    10981072</t>
    10991073<t>
     
    15561530  <c>Connection</c> <c><xref target="header.connection"/></c>
    15571531  <c>Date</c> <c><xref target="header.date"/></c>
    1558   <c>Pragma</c> <c>&header-pragma;</c>
    15591532  <c>Trailer</c> <c><xref target="header.trailer"/></c>
    15601533  <c>Transfer-Encoding</c> <c><xref target="header.transfer-encoding"/></c>
    15611534  <c>Upgrade</c> <c><xref target="header.upgrade"/></c>
    15621535  <c>Via</c> <c><xref target="header.via"/></c>
    1563   <c>Warning</c> <c>&header-warning;</c>
    1564   <c>MIME-Version</c> <c>&header-mime-version;</c>
    15651536</texttable>
    1566 <t>
    1567    General-header field names can be extended reliably only in
    1568    combination with a change in the protocol version. However, new or
    1569    experimental header fields might be given the semantics of general
    1570    header fields if all parties in the communication recognize them to
    1571    be general-header fields.
    1572 </t>
    15731537</section>
    15741538</section>
     
    27732737    <t>
    27742738        If a client will wait for a 100 (Continue) response before
    2775         sending the request body, it &MUST; send an Expect request-header
     2739        sending the request body, it &MUST; send an Expect header
    27762740        field (&header-expect;) with the "100-continue" expectation.
    27772741    </t>
    27782742    <t>
    2779         A client &MUST-NOT; send an Expect request-header field (&header-expect;)
     2743        A client &MUST-NOT; send an Expect header field (&header-expect;)
    27802744        with the "100-continue" expectation if it does not intend
    27812745        to send a request body.
     
    27952759   Requirements for HTTP/1.1 origin servers:
    27962760  <list style="symbols">
    2797     <t> Upon receiving a request which includes an Expect request-header
     2761    <t> Upon receiving a request which includes an Expect header
    27982762        field with the "100-continue" expectation, an origin server &MUST;
    27992763        either respond with 100 (Continue) status code and continue to read
     
    28062770    </t>
    28072771    <t> An origin server &SHOULD-NOT;  send a 100 (Continue) response if
    2808         the request message does not include an Expect request-header
     2772        the request message does not include an Expect header
    28092773        field with the "100-continue" expectation, and &MUST-NOT; send a
    28102774        100 (Continue) response if such a request comes from an HTTP/1.0
     
    28122776        compatibility with <xref target="RFC2068"/>, a server &MAY; send a 100 (Continue)
    28132777        status code in response to an HTTP/1.1 PUT or POST request that does
    2814         not include an Expect request-header field with the "100-continue"
     2778        not include an Expect header field with the "100-continue"
    28152779        expectation. This exception, the purpose of which is
    28162780        to minimize any client processing delays associated with an
     
    28292793    </t>
    28302794    <t> If an origin server receives a request that does not include an
    2831         Expect request-header field with the "100-continue" expectation,
     2795        Expect header field with the "100-continue" expectation,
    28322796        the request includes a request body, and the server responds
    28332797        with a final status code before reading the entire request body
     
    28452809   Requirements for HTTP/1.1 proxies:
    28462810  <list style="symbols">
    2847     <t> If a proxy receives a request that includes an Expect request-header
     2811    <t> If a proxy receives a request that includes an Expect header
    28482812        field with the "100-continue" expectation, and the proxy
    28492813        either knows that the next-hop server complies with HTTP/1.1 or
     
    28612825    <t> A proxy &MUST-NOT; forward a 100 (Continue) response if the
    28622826        request message was received from an HTTP/1.0 (or earlier)
    2863         client and did not include an Expect request-header field with
     2827        client and did not include an Expect header field with
    28642828        the "100-continue" expectation. This requirement overrides the
    28652829        general rule for forwarding of 1xx responses (see &status-1xx;).
     
    28722836<t>
    28732837   If an HTTP/1.1 client sends a request which includes a request body,
    2874    but which does not include an Expect request-header field with the
     2838   but which does not include an Expect header field with the
    28752839   "100-continue" expectation, and if the client is not directly
    28762840   connected to an HTTP/1.1 origin server, and if the client sees the
     
    28842848    </t>
    28852849    <t>
    2886       Transmit the request-header fields
     2850      Transmit the request-line, header fields, and the CRLF that
     2851      indicates the end of header fields.
    28872852    </t>
    28882853    <t>
     
    29722937  <x:anchor-alias value="Connection-v"/>
    29732938<t>
    2974    The "Connection" general-header field allows the sender to specify
     2939   The "Connection" header field allows the sender to specify
    29752940   options that are desired for that particular connection and &MUST-NOT;
    29762941   be communicated by proxies over further connections.
     
    29962961<t>
    29972962   Message header fields listed in the Connection header field &MUST-NOT; include
    2998    end-to-end header fields, such as Cache-Control.
     2963   end-to-end header fields, such as Cache-Control (&header-cache-control;).
    29992964</t>
    30002965<t>
     
    30793044  <x:anchor-alias value="Date-v"/>
    30803045<t>
    3081    The "Date" general-header field represents the date and time at which
     3046   The "Date" header field represents the date and time at which
    30823047   the message was originated, having the same semantics as the Origination
    30833048   Date Field (orig-date) defined in <xref target="RFC5322" x:fmt="of" x:sec="3.6.1"/>.
     
    31553120  <x:anchor-alias value="Host-v"/>
    31563121<t>
    3157    The "Host" request-header field specifies the Internet host and port
     3122   The "Host" header field specifies the Internet host and port
    31583123   number of the resource being requested, allowing the origin server or
    31593124   gateway to differentiate between internally-ambiguous URLs, such as the root
     
    32073172  <x:anchor-alias value="te-ext"/>
    32083173<t>
    3209    The "TE" request-header field indicates what extension transfer-codings
     3174   The "TE" header field indicates what extension transfer-codings
    32103175   it is willing to accept in the response, and whether or not it is
    32113176   willing to accept trailer fields in a chunked transfer-coding.
     
    32883253  <x:anchor-alias value="Trailer-v"/>
    32893254<t>
    3290    The "Trailer" general-header field indicates that the given set of
     3255   The "Trailer" header field indicates that the given set of
    32913256   header fields is present in the trailer of a message encoded with
    32923257   chunked transfer-coding.
     
    33243289  <x:anchor-alias value="Transfer-Encoding-v"/>
    33253290<t>
    3326    The "Transfer-Encoding" general-header field indicates what transfer-codings
     3291   The "Transfer-Encoding" header field indicates what transfer-codings
    33273292   (if any) have been applied to the message body. It differs from
    33283293   Content-Encoding (&content-codings;) in that transfer-codings are a property
     
    33593324  <x:anchor-alias value="Upgrade-v"/>
    33603325<t>
    3361    The "Upgrade" general-header field allows the client to specify what
     3326   The "Upgrade" header field allows the client to specify what
    33623327   additional communication protocols it would like to use, if the server
    33633328   chooses to switch protocols. Servers can use it to indicate what protocols
     
    34713436  <x:anchor-alias value="Via-v"/>
    34723437<t>
    3473    The "Via" general-header field &MUST; be used by gateways and proxies to
     3438   The "Via" header field &MUST; be used by gateways and proxies to
    34743439   indicate the intermediate protocols and recipients between the user
    34753440   agent and the server on requests, and between the origin server and
     
    49224887<section title="Changes to Simplify Multi-homed Web Servers and Conserve IP Addresses" anchor="changes.to.simplify.multi-homed.web.servers.and.conserve.ip.addresses">
    49234888<t>
    4924    The requirements that clients and servers support the Host request-header
     4889   The requirements that clients and servers support the Host header
    49254890   field (<xref target="header.host"/>), report an error if it is
    49264891   missing from an HTTP/1.1 request, and accept absolute URIs (<xref target="request-target"/>)
     
    49454910   requirements:
    49464911  <list style="symbols">
    4947      <t>Both clients and servers &MUST; support the Host request-header field.</t>
     4912     <t>Both clients and servers &MUST; support the Host header field.</t>
    49484913
    49494914     <t>A client that sends an HTTP/1.1 request &MUST; send a Host header field.</t>
    49504915
    49514916     <t>Servers &MUST; report a 400 (Bad Request) error if an HTTP/1.1
    4952         request does not include a Host request-header field.</t>
     4917        request does not include a Host header field.</t>
    49534918
    49544919     <t>Servers &MUST; accept absolute URIs.</t>
     
    50545019<x:ref>BWS</x:ref> = OWS
    50555020
    5056 <x:ref>Cache-Control</x:ref> = &lt;Cache-Control, defined in [Part6], Section 3.4&gt;
    50575021<x:ref>Chunked-Body</x:ref> = *chunk last-chunk trailer-part CRLF
    50585022<x:ref>Connection</x:ref> = "Connection:" OWS Connection-v
     
    50755039<x:ref>Host-v</x:ref> = uri-host [ ":" port ]
    50765040
    5077 <x:ref>MIME-Version</x:ref> = &lt;MIME-Version, defined in [Part3], Appendix A.1&gt;
    50785041<x:ref>Method</x:ref> = token
    50795042
    50805043<x:ref>OWS</x:ref> = *( [ obs-fold ] WSP )
    5081 
    5082 <x:ref>Pragma</x:ref> = &lt;Pragma, defined in [Part6], Section 3.4&gt;
    50835044
    50845045<x:ref>RWS</x:ref> = 1*( [ obs-fold ] WSP )
     
    51075068 ] *( OWS "," [ OWS received-protocol RWS received-by [ RWS comment ]
    51085069 ] )
    5109 
    5110 <x:ref>Warning</x:ref> = &lt;Warning, defined in [Part6], Section 3.6&gt;
    51115070
    51125071<x:ref>absolute-URI</x:ref> = &lt;absolute-URI, defined in [RFC3986], Section 4.3&gt;
     
    52035162<x:ref>received-protocol</x:ref> = [ protocol-name "/" ] protocol-version
    52045163<x:ref>relative-part</x:ref> = &lt;relative-part, defined in [RFC3986], Section 4.2&gt;
    5205 <x:ref>request-header</x:ref> = &lt;request-header, defined in [Part2], Section 3&gt;
    52065164<x:ref>request-target</x:ref> = "*" / absolute-URI / ( path-absolute [ "?" query ] )
    52075165 / authority
    5208 <x:ref>response-header</x:ref> = &lt;response-header, defined in [Part2], Section 5&gt;
    52095166<x:ref>rfc1123-date</x:ref> = day-name "," SP date1 SP time-of-day SP GMT
    52105167<x:ref>rfc850-date</x:ref> = day-name-l "," SP date2 SP time-of-day SP GMT
     
    52385195</figure>
    52395196<figure><preamble>ABNF diagnostics:</preamble><artwork type="inline">
    5240 ; Cache-Control defined but not used
    52415197; Chunked-Body defined but not used
    52425198; Connection defined but not used
     
    52455201; HTTP-message defined but not used
    52465202; Host defined but not used
    5247 ; MIME-Version defined but not used
    5248 ; Pragma defined but not used
    52495203; Request defined but not used
    52505204; Response defined but not used
     
    52555209; Upgrade defined but not used
    52565210; Via defined but not used
    5257 ; Warning defined but not used
    52585211; http-URI defined but not used
    52595212; https-URI defined but not used
    52605213; partial-URI defined but not used
    5261 ; request-header defined but not used
    5262 ; response-header defined but not used
    52635214; special defined but not used
    52645215</artwork></figure></section>
Note: See TracChangeset for help on using the changeset viewer.