Changeset 1772


Ignore:
Timestamp:
Jul 14, 2012, 7:09:09 AM (7 years ago)
Author:
julian.reschke@…
Message:

header -> header field (#234)

Location:
draft-ietf-httpbis/latest
Files:
11 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p0-introduction.html

    r1764 r1772  
    393393  }
    394394  @bottom-center {
    395        content: "Expires January 14, 2013";
     395       content: "Expires January 15, 2013";
    396396  }
    397397  @bottom-right {
     
    426426      <meta name="dct.creator" content="Reschke, J. F.">
    427427      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p0-introduction-latest">
    428       <meta name="dct.issued" scheme="ISO8601" content="2012-07-13">
     428      <meta name="dct.issued" scheme="ISO8601" content="2012-07-14">
    429429      <meta name="dct.abstract" content="This document is the first in a series that, collectively, define the HyperText Transfer Protocol, version 1.1; otherwise known as HTTP/1.1.">
    430430      <meta name="description" content="This document is the first in a series that, collectively, define the HyperText Transfer Protocol, version 1.1; otherwise known as HTTP/1.1.">
     
    446446            </tr>
    447447            <tr>
    448                <td class="left">Expires: January 14, 2013</td>
     448               <td class="left">Expires: January 15, 2013</td>
    449449               <td class="right">W3C</td>
    450450            </tr>
     
    467467            <tr>
    468468               <td class="left"></td>
    469                <td class="right">July 13, 2012</td>
     469               <td class="right">July 14, 2012</td>
    470470            </tr>
    471471         </tbody>
     
    490490         in progress”.
    491491      </p>
    492       <p>This Internet-Draft will expire on January 14, 2013.</p>
     492      <p>This Internet-Draft will expire on January 15, 2013.</p>
    493493      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    494494      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    529529            protocols. Also includes the HTTP and HTTPS URI schemes.
    530530         </li>
    531          <li><a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics, Payload and Content Negotiation">[Part2]</cite></a> HTTP/1.1 Core Semantics - Protocol elements such as methods, status codes, and payload-specific headers. Also includes content
    532             negotiation mechanisms.
     531         <li><a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics, Payload and Content Negotiation">[Part2]</cite></a> HTTP/1.1 Core Semantics - Protocol elements such as methods, status codes, and payload-specific header fields. Also includes
     532            content negotiation mechanisms.
    533533         </li>
    534534         <li><a href="#Part4" id="rfc.xref.Part4.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a> HTTP/1.1 Conditional Requests - An extension to make requests contingent upon their current state.
  • draft-ietf-httpbis/latest/p0-introduction.xml

    r1764 r1772  
    136136   schemes.</t>
    137137   <t><xref target="Part2"/> HTTP/1.1 Core Semantics - Protocol elements such
    138    as methods, status codes, and payload-specific headers. Also includes
     138   as methods, status codes, and payload-specific header fields. Also includes
    139139   content negotiation mechanisms.</t>
    140140   <t><xref target="Part4"/> HTTP/1.1 Conditional Requests - An extension to
  • draft-ietf-httpbis/latest/p1-messaging.html

    r1771 r1772  
    13011301            (Client Error)</a> status code if the received header field(s) would be longer than the server wishes to handle.
    13021302      </p>
    1303       <p id="rfc.section.3.2.3.p.2">A client that receives response headers that are longer than it wishes to handle can only treat it as a server error.</p>
    1304       <p id="rfc.section.3.2.3.p.3">Various ad-hoc limitations on header length are found in practice. It is <em class="bcp14">RECOMMENDED</em> that all HTTP senders and recipients support messages whose combined header fields have 4000 or more octets.
     1303      <p id="rfc.section.3.2.3.p.2">A client that receives response header fields that are longer than it wishes to handle can only treat it as a server error.</p>
     1304      <p id="rfc.section.3.2.3.p.3">Various ad-hoc limitations on header field length are found in practice. It is <em class="bcp14">RECOMMENDED</em> that all HTTP senders and recipients support messages whose combined header fields have 4000 or more octets.
    13051305      </p>
    13061306      <h3 id="rfc.section.3.2.4"><a href="#rfc.section.3.2.4">3.2.4</a>&nbsp;<a id="field.components" href="#field.components">Field value components</a></h3>
     
    16091609         </li>
    16101610         <li>the trailer fields consist entirely of optional metadata, and the recipient could use the message (in a manner acceptable
    1611             to the server where the field originated) without receiving it. In other words, the server that generated the header (often
    1612             but not always the origin server) is willing to accept the possibility that the trailer fields might be silently discarded
     1611            to the server where the field originated) without receiving it. In other words, the server that generated the header field
     1612            (often but not always the origin server) is willing to accept the possibility that the trailer fields might be silently discarded
    16131613            along the path to the client.
    16141614         </li>
     
    29762976      <p id="rfc.section.A.1.2.p.2">Some clients and servers might wish to be compatible with these previous approaches to persistent connections, by explicitly
    29772977         negotiating for them with a "Connection: keep-alive" request header field. However, some experimental implementations of HTTP/1.0
    2978          persistent connections are faulty; for example, if a HTTP/1.0 proxy server doesn't understand <a href="#header.connection" class="smpl">Connection</a>, it will erroneously forward that header to the next inbound server, which would result in a hung connection.
    2979       </p>
    2980       <p id="rfc.section.A.1.2.p.3">One attempted solution was the introduction of a Proxy-Connection header, targeted specifically at proxies. In practice, this
    2981          was also unworkable, because proxies are often deployed in multiple layers, bringing about the same problem discussed above.
    2982       </p>
    2983       <p id="rfc.section.A.1.2.p.4">As a result, clients are encouraged not to send the Proxy-Connection header in any requests.</p>
     2978         persistent connections are faulty; for example, if a HTTP/1.0 proxy server doesn't understand <a href="#header.connection" class="smpl">Connection</a>, it will erroneously forward that header field to the next inbound server, which would result in a hung connection.
     2979      </p>
     2980      <p id="rfc.section.A.1.2.p.3">One attempted solution was the introduction of a Proxy-Connection header field, targeted specifically at proxies. In practice,
     2981         this was also unworkable, because proxies are often deployed in multiple layers, bringing about the same problem discussed
     2982         above.
     2983      </p>
     2984      <p id="rfc.section.A.1.2.p.4">As a result, clients are encouraged not to send the Proxy-Connection header field in any requests.</p>
    29842985      <p id="rfc.section.A.1.2.p.5">Clients are also encouraged to consider the use of Connection: keep-alive in requests carefully; while they can enable persistent
    29852986         connections with HTTP/1.0 servers, clients using them need will need to monitor the connection for "hung" requests (which
    2986          indicate that the client ought stop sending the header), and this mechanism ought not be used by clients at all when a proxy
    2987          is being used.
     2987         indicate that the client ought stop sending the header field), and this mechanism ought not be used by clients at all when
     2988         a proxy is being used.
    29882989      </p>
    29892990      <h3 id="rfc.section.A.1.3"><a href="#rfc.section.A.1.3">A.1.3</a>&nbsp;<a id="introduction.of.transfer-encoding" href="#introduction.of.transfer-encoding">Introduction of Transfer-Encoding</a></h3>
     
    32583259      </p>
    32593260      <ul>
    3260          <li>Reference RFC 3984, and update header field registrations for headers defined in this document.</li>
     3261         <li>Reference RFC 3984, and update header field registrations for header fields defined in this document.</li>
    32613262      </ul>
    32623263      <p id="rfc.section.C.4.p.3">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
     
    32783279         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/128">http://tools.ietf.org/wg/httpbis/trac/ticket/128</a>&gt;: "Cite HTTPS URI scheme definition"
    32793280         </li>
    3280          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/129">http://tools.ietf.org/wg/httpbis/trac/ticket/129</a>&gt;: "List-type headers vs Set-Cookie"
     3281         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/129">http://tools.ietf.org/wg/httpbis/trac/ticket/129</a>&gt;: "List-type header fields vs Set-Cookie"
    32813282         </li>
    32823283      </ul>
     
    33593360      <p id="rfc.section.C.9.p.1">Closed issues: </p>
    33603361      <ul>
    3361          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/93">http://tools.ietf.org/wg/httpbis/trac/ticket/93</a>&gt;: "Repeating single-value headers"
     3362         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/93">http://tools.ietf.org/wg/httpbis/trac/ticket/93</a>&gt;: "Repeating single-value header fields"
    33623363         </li>
    33633364         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/131">http://tools.ietf.org/wg/httpbis/trac/ticket/131</a>&gt;: "increase connection limit"
     
    33933394         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/60">http://tools.ietf.org/wg/httpbis/trac/ticket/60</a>&gt;: "Placement of 13.5.1 and 13.5.2"
    33943395         </li>
    3395          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/200">http://tools.ietf.org/wg/httpbis/trac/ticket/200</a>&gt;: "use of term "word" when talking about header structure"
     3396         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/200">http://tools.ietf.org/wg/httpbis/trac/ticket/200</a>&gt;: "use of term "word" when talking about header field structure"
    33963397         </li>
    33973398      </ul>
     
    34093410         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/165">http://tools.ietf.org/wg/httpbis/trac/ticket/165</a>&gt;: "Case-sensitivity of HTTP-date"
    34103411         </li>
    3411          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/200">http://tools.ietf.org/wg/httpbis/trac/ticket/200</a>&gt;: "use of term "word" when talking about header structure"
     3412         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/200">http://tools.ietf.org/wg/httpbis/trac/ticket/200</a>&gt;: "use of term "word" when talking about header field structure"
    34123413         </li>
    34133414      </ul>
     
    34243425         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/90">http://tools.ietf.org/wg/httpbis/trac/ticket/90</a>&gt;: "Delimiting messages with multipart/byteranges"
    34253426         </li>
    3426          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/95">http://tools.ietf.org/wg/httpbis/trac/ticket/95</a>&gt;: "Handling multiple Content-Length headers"
     3427         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/95">http://tools.ietf.org/wg/httpbis/trac/ticket/95</a>&gt;: "Handling multiple Content-Length header fields"
    34273428         </li>
    34283429         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/109">http://tools.ietf.org/wg/httpbis/trac/ticket/109</a>&gt;: "Clarify entity / representation / variant terminology"
     
    34503451      <p id="rfc.section.C.13.p.2">Partly resolved issues: </p>
    34513452      <ul>
    3452          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/95">http://tools.ietf.org/wg/httpbis/trac/ticket/95</a>&gt;: "Handling multiple Content-Length headers"
     3453         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/95">http://tools.ietf.org/wg/httpbis/trac/ticket/95</a>&gt;: "Handling multiple Content-Length header fields"
    34533454         </li>
    34543455      </ul>
     
    34623463         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/210">http://tools.ietf.org/wg/httpbis/trac/ticket/210</a>&gt;: "define 'transparent' proxy"
    34633464         </li>
    3464          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/224">http://tools.ietf.org/wg/httpbis/trac/ticket/224</a>&gt;: "Header Classification"
     3465         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/224">http://tools.ietf.org/wg/httpbis/trac/ticket/224</a>&gt;: "Header Field Classification"
    34653466         </li>
    34663467         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/233">http://tools.ietf.org/wg/httpbis/trac/ticket/233</a>&gt;: "Is * usable as a request-uri for new methods?"
     
    34783479         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/53">http://tools.ietf.org/wg/httpbis/trac/ticket/53</a>&gt;: "Allow is not in 13.5.2"
    34793480         </li>
    3480          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/95">http://tools.ietf.org/wg/httpbis/trac/ticket/95</a>&gt;: "Handling multiple Content-Length headers"
     3481         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/95">http://tools.ietf.org/wg/httpbis/trac/ticket/95</a>&gt;: "Handling multiple Content-Length header fields"
    34813482         </li>
    34823483         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/276">http://tools.ietf.org/wg/httpbis/trac/ticket/276</a>&gt;: "untangle ABNFs for header fields"
     
    35143515         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/186">http://tools.ietf.org/wg/httpbis/trac/ticket/186</a>&gt;: "Document HTTP's error-handling philosophy"
    35153516         </li>
    3516          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/215">http://tools.ietf.org/wg/httpbis/trac/ticket/215</a>&gt;: "Explain header registration"
     3517         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/215">http://tools.ietf.org/wg/httpbis/trac/ticket/215</a>&gt;: "Explain header field registration"
    35173518         </li>
    35183519         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/219">http://tools.ietf.org/wg/httpbis/trac/ticket/219</a>&gt;: "Revise Acknowledgements Sections"
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r1771 r1772  
    13521352</t>
    13531353<t>
    1354    A client that receives response headers that are longer than it wishes to
    1355    handle can only treat it as a server error.
    1356 </t>
    1357 <t>
    1358    Various ad-hoc limitations on header length are found in practice. It is
    1359    &RECOMMENDED; that all HTTP senders and recipients support messages whose
     1354   A client that receives response header fields that are longer than it wishes
     1355   to handle can only treat it as a server error.
     1356</t>
     1357<t>
     1358   Various ad-hoc limitations on header field length are found in practice. It
     1359   is &RECOMMENDED; that all HTTP senders and recipients support messages whose
    13601360   combined header fields have 4000 or more octets.
    13611361</t>
     
    19961996    recipient could use the message (in a manner acceptable to the server where
    19971997    the field originated) without receiving it. In other words, the server that
    1998     generated the header (often but not always the origin server) is willing to
    1999     accept the possibility that the trailer fields might be silently discarded
    2000     along the path to the client.</t>
     1998    generated the header field (often but not always the origin server) is
     1999    willing to accept the possibility that the trailer fields might be silently
     2000    discarded along the path to the client.</t>
    20012001  </list>
    20022002</t>
     
    49744974   experimental implementations of HTTP/1.0 persistent connections are faulty;
    49754975   for example, if a HTTP/1.0 proxy server doesn't understand
    4976    <x:ref>Connection</x:ref>, it will erroneously forward that header to the
    4977    next inbound server, which would result in a hung connection.
    4978 </t>
    4979 <t>
    4980    One attempted solution was the introduction of a Proxy-Connection header,
    4981    targeted specifically at proxies. In practice, this was also unworkable,
    4982    because proxies are often deployed in multiple layers, bringing about the
    4983    same problem discussed above.
     4976   <x:ref>Connection</x:ref>, it will erroneously forward that header field
     4977   to the next inbound server, which would result in a hung connection.
     4978</t>
     4979<t>
     4980   One attempted solution was the introduction of a Proxy-Connection header
     4981   field, targeted specifically at proxies. In practice, this was also
     4982   unworkable, because proxies are often deployed in multiple layers, bringing
     4983   about the same problem discussed above.
    49844984</t>
    49854985<t>
    49864986   As a result, clients are encouraged not to send the Proxy-Connection header
    4987    in any requests.
     4987   field in any requests.
    49884988</t>
    49894989<t>
     
    49924992   HTTP/1.0 servers, clients using them need will need to monitor the
    49934993   connection for "hung" requests (which indicate that the client ought stop
    4994    sending the header), and this mechanism ought not be used by clients at all
    4995    when a proxy is being used.
     4994   sending the header field), and this mechanism ought not be used by clients
     4995   at all when a proxy is being used.
    49964996</t>
    49974997</section>
     
    54315431  <list style="symbols">
    54325432    <t>
    5433       Reference RFC 3984, and update header field registrations for headers defined
    5434       in this document.
     5433      Reference RFC 3984, and update header field registrations for header
     5434      fields defined in this document.
    54355435    </t>
    54365436  </list>
     
    54725472    <t>
    54735473      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/129"/>:
    5474       "List-type headers vs Set-Cookie"
     5474      "List-type header fields vs Set-Cookie"
    54755475    </t>
    54765476  </list>
     
    56345634    <t>
    56355635      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/93"/>:
    5636       "Repeating single-value headers"
     5636      "Repeating single-value header fields"
    56375637    </t>
    56385638    <t>
     
    57015701    <t>
    57025702      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/200"/>:
    5703       "use of term "word" when talking about header structure"
     5703      "use of term "word" when talking about header field structure"
    57045704    </t>
    57055705  </list>
     
    57335733    <t>
    57345734      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/200"/>:
    5735       "use of term "word" when talking about header structure"
     5735      "use of term "word" when talking about header field structure"
    57365736    </t>
    57375737  </list>
     
    57625762    <t>
    57635763      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/95"/>:
    5764       "Handling multiple Content-Length headers"
     5764      "Handling multiple Content-Length header fields"
    57655765    </t>
    57665766    <t>
     
    58125812    <t>
    58135813      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/95"/>:
    5814       "Handling multiple Content-Length headers"
     5814      "Handling multiple Content-Length header fields"
    58155815    </t>
    58165816  </list>
     
    58365836    <t>
    58375837      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/224"/>:
    5838       "Header Classification"
     5838      "Header Field Classification"
    58395839    </t>
    58405840    <t>
     
    58685868    <t>
    58695869      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/95"/>:
    5870       "Handling multiple Content-Length headers"
     5870      "Handling multiple Content-Length header fields"
    58715871    </t>
    58725872    <t>
     
    59405940    <t>
    59415941      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/215"/>:
    5942       "Explain header registration"
     5942      "Explain header field registration"
    59435943    </t>
    59445944    <t>
  • draft-ietf-httpbis/latest/p2-semantics.html

    r1770 r1772  
    12191219         </li>
    12201220         <li>
    1221             <p>How the header might interact with caching (see <a href="#Part6" id="rfc.xref.Part6.7"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).
     1221            <p>How the header field might interact with caching (see <a href="#Part6" id="rfc.xref.Part6.7"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).
    12221222            </p>
    12231223         </li>
     
    16461646      </p>
    16471647      <p id="rfc.section.4.2.1.p.3">Definitions of new HTTP status codes typically explain the request conditions that produce a response containing the status
    1648          code (e.g., combinations of request headers and/or method(s)), along with any interactions with response headers (e.g., those
    1649          that are required, those that modify the semantics of the response).
     1648         code (e.g., combinations of request header fields and/or method(s)), along with any interactions with response header fields
     1649         (e.g., those that are required, those that modify the semantics of the response).
    16501650      </p>
    16511651      <p id="rfc.section.4.2.1.p.4">New HTTP status codes are required to fall under one of the categories defined in <a href="#status.codes" title="Status Codes">Section&nbsp;4</a>. To allow existing parsers to properly handle them, new status codes cannot disallow a response body, although they can mandate
    1652          a zero-length response body. They can require the presence of one or more particular HTTP response header(s).
     1652         a zero-length response body. They can require the presence of one or more particular HTTP response header field(s).
    16531653      </p>
    16541654      <p id="rfc.section.4.2.1.p.5">Likewise, their definitions can specify that caches are allowed to use heuristics to determine their freshness (see <a href="#Part6" id="rfc.xref.Part6.10"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>; by default, it is not allowed), and can define how to determine the resource which they carry a representation for (see <a href="#identifying.response.associated.with.representation" title="Identifying the Resource Associated with a Representation">Section&nbsp;7.1</a>; by default, it is anonymous).
     
    36683668         of individual users. Note that for many users not behind a proxy, the network address of the host running the user agent will
    36693669         also serve as a long-lived user identifier. In environments where proxies are used to enhance privacy, user agents ought to
    3670          be conservative in offering accept header configuration options to end users. As an extreme privacy measure, proxies could
    3671          filter the accept header fields in relayed requests. General purpose user agents which provide a high degree of header configurability <em class="bcp14">SHOULD</em> warn users about the loss of privacy which can be involved.
     3670         be conservative in offering accept header field configuration options to end users. As an extreme privacy measure, proxies
     3671         could filter the accept header fields in relayed requests. General purpose user agents which provide a high degree of header
     3672         field configurability <em class="bcp14">SHOULD</em> warn users about the loss of privacy which can be involved.
    36723673      </p>
    36733674      <h1 id="rfc.section.12"><a href="#rfc.section.12">12.</a>&nbsp;<a id="acks" href="#acks">Acknowledgments</a></h1>
     
    42534254         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/76">http://tools.ietf.org/wg/httpbis/trac/ticket/76</a>&gt;: "305 Use Proxy"
    42544255         </li>
    4255          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/105">http://tools.ietf.org/wg/httpbis/trac/ticket/105</a>&gt;: "Classification for Allow header"
     4256         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/105">http://tools.ietf.org/wg/httpbis/trac/ticket/105</a>&gt;: "Classification for Allow header field"
    42564257         </li>
    42574258         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/112">http://tools.ietf.org/wg/httpbis/trac/ticket/112</a>&gt;: "PUT - 'store under' vs 'store at'"
     
    42614262      </p>
    42624263      <ul>
    4263          <li>Reference RFC 3984, and update header field registrations for headers defined in this document.</li>
     4264         <li>Reference RFC 3984, and update header field registrations for header fields defined in this document.</li>
    42644265      </ul>
    42654266      <p id="rfc.section.E.6.p.3">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
     
    42734274         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/67">http://tools.ietf.org/wg/httpbis/trac/ticket/67</a>&gt;: "Quoting Charsets"
    42744275         </li>
    4275          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/105">http://tools.ietf.org/wg/httpbis/trac/ticket/105</a>&gt;: "Classification for Allow header"
     4276         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/105">http://tools.ietf.org/wg/httpbis/trac/ticket/105</a>&gt;: "Classification for Allow header field"
    42764277         </li>
    42774278         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/115">http://tools.ietf.org/wg/httpbis/trac/ticket/115</a>&gt;: "missing default for qvalue in description of Accept-Encoding"
     
    42814282      </p>
    42824283      <ul>
    4283          <li>Reference RFC 3984, and update header field registrations for headers defined in this document.</li>
     4284         <li>Reference RFC 3984, and update header field registrations for header fields defined in this document.</li>
    42844285      </ul>
    42854286      <h2 id="rfc.section.E.8"><a href="#rfc.section.E.8">E.8</a>&nbsp;<a id="changes.since.03" href="#changes.since.03">Since draft-ietf-httpbis-p2-semantics-03</a></h2>
     
    43984399         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/182">http://tools.ietf.org/wg/httpbis/trac/ticket/182</a>&gt;: "update note about redirect limit"
    43994400         </li>
    4400          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/191">http://tools.ietf.org/wg/httpbis/trac/ticket/191</a>&gt;: "Location header ABNF should use 'URI'"
     4401         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/191">http://tools.ietf.org/wg/httpbis/trac/ticket/191</a>&gt;: "Location header field ABNF should use 'URI'"
    44014402         </li>
    44024403         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/192">http://tools.ietf.org/wg/httpbis/trac/ticket/192</a>&gt;: "fragments in Location vs status 303"
     
    44554456      <p id="rfc.section.E.20.p.2">Partly resolved issues: </p>
    44564457      <ul>
    4457          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/185">http://tools.ietf.org/wg/httpbis/trac/ticket/185</a>&gt;: "Location header payload handling"
     4458         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/185">http://tools.ietf.org/wg/httpbis/trac/ticket/185</a>&gt;: "Location header field payload handling"
    44584459         </li>
    44594460         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/196">http://tools.ietf.org/wg/httpbis/trac/ticket/196</a>&gt;: "Term for the requested resource's URI"
     
    44694470         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/155">http://tools.ietf.org/wg/httpbis/trac/ticket/155</a>&gt;: "Content Sniffing"
    44704471         </li>
    4471          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/200">http://tools.ietf.org/wg/httpbis/trac/ticket/200</a>&gt;: "use of term "word" when talking about header structure"
     4472         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/200">http://tools.ietf.org/wg/httpbis/trac/ticket/200</a>&gt;: "use of term "word" when talking about header field structure"
    44724473         </li>
    44734474      </ul>
     
    45484549         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/103">http://tools.ietf.org/wg/httpbis/trac/ticket/103</a>&gt;: "Content-*"
    45494550         </li>
    4550          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/104">http://tools.ietf.org/wg/httpbis/trac/ticket/104</a>&gt;: "Header type defaulting"
     4551         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/104">http://tools.ietf.org/wg/httpbis/trac/ticket/104</a>&gt;: "Header field type defaulting"
    45514552         </li>
    45524553         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/112">http://tools.ietf.org/wg/httpbis/trac/ticket/112</a>&gt;: "PUT - 'store under' vs 'store at'"
     
    45544555         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/137">http://tools.ietf.org/wg/httpbis/trac/ticket/137</a>&gt;: "duplicate ABNF for reason-phrase"
    45554556         </li>
    4556          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/180">http://tools.ietf.org/wg/httpbis/trac/ticket/180</a>&gt;: "Note special status of Content-* prefix in header registration procedures"
     4557         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/180">http://tools.ietf.org/wg/httpbis/trac/ticket/180</a>&gt;: "Note special status of Content-* prefix in header field registration procedures"
    45574558         </li>
    45584559         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/203">http://tools.ietf.org/wg/httpbis/trac/ticket/203</a>&gt;: "Max-Forwards vs extension methods"
     
    45604561         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/213">http://tools.ietf.org/wg/httpbis/trac/ticket/213</a>&gt;: "What is the value space of HTTP status codes?" (actually fixed in draft-ietf-httpbis-p2-semantics-11)
    45614562         </li>
    4562          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/224">http://tools.ietf.org/wg/httpbis/trac/ticket/224</a>&gt;: "Header Classification"
     4563         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/224">http://tools.ietf.org/wg/httpbis/trac/ticket/224</a>&gt;: "Header Field Classification"
    45634564         </li>
    45644565         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/225">http://tools.ietf.org/wg/httpbis/trac/ticket/225</a>&gt;: "PUT side effect: invalidation or just stale?"
     
    45804581      <p id="rfc.section.E.27.p.1">Closed issues: </p>
    45814582      <ul>
    4582          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/224">http://tools.ietf.org/wg/httpbis/trac/ticket/224</a>&gt;: "Header Classification"
     4583         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/224">http://tools.ietf.org/wg/httpbis/trac/ticket/224</a>&gt;: "Header Field Classification"
    45834584         </li>
    45844585         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/276">http://tools.ietf.org/wg/httpbis/trac/ticket/276</a>&gt;: "untangle ABNFs for header fields"
     
    46424643         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/186">http://tools.ietf.org/wg/httpbis/trac/ticket/186</a>&gt;: "Document HTTP's error-handling philosophy"
    46434644         </li>
    4644          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/231">http://tools.ietf.org/wg/httpbis/trac/ticket/231</a>&gt;: "Considerations for new headers"
     4645         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/231">http://tools.ietf.org/wg/httpbis/trac/ticket/231</a>&gt;: "Considerations for new header fields"
    46454646         </li>
    46464647         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/310">http://tools.ietf.org/wg/httpbis/trac/ticket/310</a>&gt;: "clarify 303 redirect on HEAD"
     
    46564657      <p id="rfc.section.E.36.p.1">Closed issues: </p>
    46574658      <ul>
    4658          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/185">http://tools.ietf.org/wg/httpbis/trac/ticket/185</a>&gt;: "Location header payload handling"
     4659         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/185">http://tools.ietf.org/wg/httpbis/trac/ticket/185</a>&gt;: "Location header field payload handling"
    46594660         </li>
    46604661         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/255">http://tools.ietf.org/wg/httpbis/trac/ticket/255</a>&gt;: "Clarify status code for rate limiting" (change backed out because a new status code is being defined for this purpose)
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r1770 r1772  
    10751075    <x:lt><t>Under what conditions intermediaries are allowed to modify the header
    10761076    field's value, insert or delete it.</t></x:lt>
    1077     <x:lt><t>How the header might interact with caching (see <xref target="Part6"/>).</t></x:lt>
     1077    <x:lt><t>How the header field might interact with caching (see
     1078    <xref target="Part6"/>).</t></x:lt>
    10781079    <x:lt><t>Whether the header field is useful or allowable in trailers (see
    10791080    &chunked-encoding;).</t></x:lt>
     
    12901291   Definitions of new HTTP status codes typically explain the request
    12911292   conditions that produce a response containing the status code (e.g.,
    1292    combinations of request headers and/or method(s)), along with any
    1293    interactions with response headers (e.g., those that are required, those
    1294    that modify the semantics of the response).
     1293   combinations of request header fields and/or method(s)), along with any
     1294   interactions with response header fields (e.g., those that are required,
     1295   those that modify the semantics of the response).
    12951296</t>
    12961297<t>
     
    12991300   properly handle them, new status codes cannot disallow a response body,
    13001301   although they can mandate a zero-length response body. They can require the
    1301    presence of one or more particular HTTP response header(s).
     1302   presence of one or more particular HTTP response header field(s).
    13021303</t>
    13031304<t>
     
    46214622   identifier. In environments where proxies are used to enhance
    46224623   privacy, user agents ought to be conservative in offering accept
    4623    header configuration options to end users. As an extreme privacy
     4624   header field configuration options to end users. As an extreme privacy
    46244625   measure, proxies could filter the accept header fields in relayed requests.
    4625    General purpose user agents which provide a high degree of header
     4626   General purpose user agents which provide a high degree of header field
    46264627   configurability &SHOULD; warn users about the loss of privacy which can
    46274628   be involved.
     
    59805981    <t>
    59815982      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/105"/>:
    5982       "Classification for Allow header"
     5983      "Classification for Allow header field"
    59835984    </t>
    59845985    <t>
     
    59925993  <list style="symbols">
    59935994    <t>
    5994       Reference RFC 3984, and update header field registrations for headers defined
    5995       in this document.
     5995      Reference RFC 3984, and update header field registrations for header
     5996      fields defined in this document.
    59965997    </t>
    59975998  </list>
     
    60176018    <t>
    60186019      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/105"/>:
    6019       "Classification for Allow header"
     6020      "Classification for Allow header field"
    60206021    </t>
    60216022    <t>
     
    60296030  <list style="symbols">
    60306031    <t>
    6031       Reference RFC 3984, and update header field registrations for headers defined
    6032       in this document.
     6032      Reference RFC 3984, and update header field registrations for header
     6033      fields defined in this document.
    60336034    </t>
    60346035  </list>
     
    62656266    <t>
    62666267      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/191"/>:
    6267       "Location header ABNF should use 'URI'"
     6268      "Location header field ABNF should use 'URI'"
    62686269    </t>
    62696270    <t>
     
    63796380    <t>
    63806381      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/185"/>:
    6381       "Location header payload handling"
     6382      "Location header field payload handling"
    63826383    </t>
    63836384    <t>
     
    64076408    <t>
    64086409      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/200"/>:
    6409       "use of term "word" when talking about header structure"
     6410      "use of term "word" when talking about header field structure"
    64106411    </t>
    64116412  </list>
     
    65636564    <t>
    65646565      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/104"/>:
    6565       "Header type defaulting"
     6566      "Header field type defaulting"
    65666567    </t>
    65676568    <t>
     
    65756576    <t>
    65766577      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/180"/>:
    6577       "Note special status of Content-* prefix in header registration procedures"
     6578      "Note special status of Content-* prefix in header field registration procedures"
    65786579    </t>
    65796580    <t>
     
    65886589    <t>
    65896590      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/224"/>:
    6590       "Header Classification"
     6591      "Header Field Classification"
    65916592    </t>
    65926593    <t>
     
    66286629    <t>
    66296630      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/224"/>:
    6630       "Header Classification"
     6631      "Header Field Classification"
    66316632    </t>
    66326633    <t>
     
    67546755    <t>
    67556756      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/231"/>:
    6756       "Considerations for new headers"
     6757      "Considerations for new header fields"
    67576758    </t>
    67586759    <t>
     
    67826783    <t>
    67836784      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/185"/>:
    6784       "Location header payload handling"
     6785      "Location header field payload handling"
    67856786    </t>
    67866787    <t>
  • draft-ietf-httpbis/latest/p4-conditional.html

    r1770 r1772  
    794794      <div id="rfc.iref.h.2"></div>
    795795      <h2 id="rfc.section.2.3"><a href="#rfc.section.2.3">2.3</a>&nbsp;<a id="header.etag" href="#header.etag">ETag</a></h2>
    796       <p id="rfc.section.2.3.p.1">The ETag header field provides the current entity-tag for the selected representation. An entity-tag is an opaque validator
     796      <p id="rfc.section.2.3.p.1">The "ETag" header field provides the current entity-tag for the selected representation. An entity-tag is an opaque validator
    797797         for differentiating between multiple representations of the same resource, regardless of whether those multiple representations
    798798         are due to resource state changes over time, content negotiation resulting in multiple representations being valid at the
  • draft-ietf-httpbis/latest/p4-conditional.xml

    r1770 r1772  
    482482  <x:anchor-alias value="etagc"/>
    483483<t>
    484    The ETag header field provides the current entity-tag for the
     484   The "ETag" header field provides the current entity-tag for the
    485485   selected representation.
    486486   An entity-tag is an opaque validator for differentiating between
  • draft-ietf-httpbis/latest/p5-range.xml

    r1770 r1772  
    525525</artwork></figure>
    526526<t>
    527       Origin servers that accept byte-range requests &MAY; send
     527   Origin servers that accept byte-range requests &MAY; send
    528528</t>
    529529<figure><artwork type="example">
     
    531531</artwork></figure>
    532532<t>
    533       but are not required to do so. Clients &MAY; generate range
    534       requests without having received this header field for the resource
    535       involved. Range units are defined in <xref target="range.units"/>.
    536 </t>
    537 <t>
    538       Servers that do not accept any kind of range request for a
    539       resource &MAY; send
     533   but are not required to do so. Clients &MAY; generate range
     534   requests without having received this header field for the resource
     535   involved. Range units are defined in <xref target="range.units"/>.
     536</t>
     537<t>
     538   Servers that do not accept any kind of range request for a
     539   resource &MAY; send
    540540</t>
    541541<figure><artwork type="example">
     
    543543</artwork></figure>
    544544<t>
    545       to advise the client not to attempt a range request.
     545   to advise the client not to attempt a range request.
    546546</t>
    547547</section>
  • draft-ietf-httpbis/latest/p6-cache.html

    r1770 r1772  
    11881188      <p id="rfc.section.5.p.2">If one or more stored GET responses can be selected (as per <a href="#caching.negotiated.responses" title="Using Negotiated Responses">Section&nbsp;4.3</a>) for a HEAD request, and the <a href="p1-messaging.html#header.content-length" class="smpl">Content-Length</a>, <a href="p4-conditional.html#header.etag" class="smpl">ETag</a> or <a href="p4-conditional.html#header.last-modified" class="smpl">Last-Modified</a> value of a HEAD response differs from that in a selected GET response, the cache <em class="bcp14">MUST</em> consider that selected response to be stale.
    11891189      </p>
    1190       <p id="rfc.section.5.p.3">If the <a href="p1-messaging.html#header.content-length" class="smpl">Content-Length</a>, <a href="p4-conditional.html#header.etag" class="smpl">ETag</a> and <a href="p4-conditional.html#header.last-modified" class="smpl">Last-Modified</a> values of a HEAD response (when present) are the same as that in a selected GET response (as per <a href="#caching.negotiated.responses" title="Using Negotiated Responses">Section&nbsp;4.3</a>), the cache <em class="bcp14">SHOULD</em> update the remaining headers in the stored response using the following rules:
     1190      <p id="rfc.section.5.p.3">If the <a href="p1-messaging.html#header.content-length" class="smpl">Content-Length</a>, <a href="p4-conditional.html#header.etag" class="smpl">ETag</a> and <a href="p4-conditional.html#header.last-modified" class="smpl">Last-Modified</a> values of a HEAD response (when present) are the same as that in a selected GET response (as per <a href="#caching.negotiated.responses" title="Using Negotiated Responses">Section&nbsp;4.3</a>), the cache <em class="bcp14">SHOULD</em> update the remaining header fields in the stored response using the following rules:
    11911191      </p>
    11921192      <ul>
     
    15911591      </p>
    15921592      <p id="rfc.section.7.6.p.7">Systems that generate multiple Warning header fields are encouraged to order them with this user agent behavior in mind. New
    1593          Warning header fields are added after any existing Warning headers fields.
     1593         Warning header fields are added after any existing Warning header fields.
    15941594      </p>
    15951595      <p id="rfc.section.7.6.p.8">Warnings are assigned three digit warn-codes. The first digit indicates whether the Warning is required to be deleted from
     
    20512051         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/307">http://tools.ietf.org/wg/httpbis/trac/ticket/307</a>&gt;: "untangle Cache-Control ABNF"
    20522052         </li>
    2053          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/353">http://tools.ietf.org/wg/httpbis/trac/ticket/353</a>&gt;: "Multiple values in Cache-Control headers"
     2053         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/353">http://tools.ietf.org/wg/httpbis/trac/ticket/353</a>&gt;: "Multiple values in Cache-Control header fields"
    20542054         </li>
    20552055         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/355">http://tools.ietf.org/wg/httpbis/trac/ticket/355</a>&gt;: "Case sensitivity of header fields in CC values"
  • draft-ietf-httpbis/latest/p6-cache.xml

    r1770 r1772  
    11331133   the same as that in a selected GET response (as per
    11341134   <xref target="caching.negotiated.responses"/>), the cache &SHOULD; update
    1135    the remaining headers in the stored response using the following rules:
     1135   the remaining header fields in the stored response using the following
     1136   rules:
    11361137   <list style="symbols">
    11371138      <t>delete any <x:ref>Warning</x:ref> header fields in the stored response
     
    19241925   Systems that generate multiple Warning header fields are encouraged to
    19251926   order them with this user agent behavior in mind. New Warning header fields
    1926    are added after any existing Warning headers fields.
     1927   are added after any existing Warning header fields.
    19271928</t>
    19281929<t>
     
    26722673    <t>
    26732674      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/353"/>:
    2674       "Multiple values in Cache-Control headers"
     2675      "Multiple values in Cache-Control header fields"
    26752676    </t>
    26762677    <t>
Note: See TracChangeset for help on using the changeset viewer.