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

header -> header field (#234)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • 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"
Note: See TracChangeset for help on using the changeset viewer.