Changeset 1772 for draft-ietf-httpbis/latest/p1-messaging.html
- Timestamp:
- 14/07/12 14:09:09 (11 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r1771 r1772 1301 1301 (Client Error)</a> status code if the received header field(s) would be longer than the server wishes to handle. 1302 1302 </p> 1303 <p id="rfc.section.3.2.3.p.2">A client that receives response header s 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. 1305 1305 </p> 1306 1306 <h3 id="rfc.section.3.2.4"><a href="#rfc.section.3.2.4">3.2.4</a> <a id="field.components" href="#field.components">Field value components</a></h3> … … 1609 1609 </li> 1610 1610 <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 (often1612 but not always the origin server) is willing to accept the possibility that the trailer fields might be silently discarded1611 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 1613 1613 along the path to the client. 1614 1614 </li> … … 2976 2976 <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 2977 2977 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> 2984 2985 <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 2985 2986 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 proxy2987 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. 2988 2989 </p> 2989 2990 <h3 id="rfc.section.A.1.3"><a href="#rfc.section.A.1.3">A.1.3</a> <a id="introduction.of.transfer-encoding" href="#introduction.of.transfer-encoding">Introduction of Transfer-Encoding</a></h3> … … 3258 3259 </p> 3259 3260 <ul> 3260 <li>Reference RFC 3984, and update header field registrations for header s defined in this document.</li>3261 <li>Reference RFC 3984, and update header field registrations for header fields defined in this document.</li> 3261 3262 </ul> 3262 3263 <p id="rfc.section.C.4.p.3">Ongoing work on ABNF conversion (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>>): … … 3278 3279 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/128">http://tools.ietf.org/wg/httpbis/trac/ticket/128</a>>: "Cite HTTPS URI scheme definition" 3279 3280 </li> 3280 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/129">http://tools.ietf.org/wg/httpbis/trac/ticket/129</a>>: "List-type header s vs Set-Cookie"3281 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/129">http://tools.ietf.org/wg/httpbis/trac/ticket/129</a>>: "List-type header fields vs Set-Cookie" 3281 3282 </li> 3282 3283 </ul> … … 3359 3360 <p id="rfc.section.C.9.p.1">Closed issues: </p> 3360 3361 <ul> 3361 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/93">http://tools.ietf.org/wg/httpbis/trac/ticket/93</a>>: "Repeating single-value header s"3362 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/93">http://tools.ietf.org/wg/httpbis/trac/ticket/93</a>>: "Repeating single-value header fields" 3362 3363 </li> 3363 3364 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/131">http://tools.ietf.org/wg/httpbis/trac/ticket/131</a>>: "increase connection limit" … … 3393 3394 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/60">http://tools.ietf.org/wg/httpbis/trac/ticket/60</a>>: "Placement of 13.5.1 and 13.5.2" 3394 3395 </li> 3395 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/200">http://tools.ietf.org/wg/httpbis/trac/ticket/200</a>>: "use of term "word" when talking about header structure"3396 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/200">http://tools.ietf.org/wg/httpbis/trac/ticket/200</a>>: "use of term "word" when talking about header field structure" 3396 3397 </li> 3397 3398 </ul> … … 3409 3410 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/165">http://tools.ietf.org/wg/httpbis/trac/ticket/165</a>>: "Case-sensitivity of HTTP-date" 3410 3411 </li> 3411 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/200">http://tools.ietf.org/wg/httpbis/trac/ticket/200</a>>: "use of term "word" when talking about header structure"3412 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/200">http://tools.ietf.org/wg/httpbis/trac/ticket/200</a>>: "use of term "word" when talking about header field structure" 3412 3413 </li> 3413 3414 </ul> … … 3424 3425 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/90">http://tools.ietf.org/wg/httpbis/trac/ticket/90</a>>: "Delimiting messages with multipart/byteranges" 3425 3426 </li> 3426 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/95">http://tools.ietf.org/wg/httpbis/trac/ticket/95</a>>: "Handling multiple Content-Length header s"3427 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/95">http://tools.ietf.org/wg/httpbis/trac/ticket/95</a>>: "Handling multiple Content-Length header fields" 3427 3428 </li> 3428 3429 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/109">http://tools.ietf.org/wg/httpbis/trac/ticket/109</a>>: "Clarify entity / representation / variant terminology" … … 3450 3451 <p id="rfc.section.C.13.p.2">Partly resolved issues: </p> 3451 3452 <ul> 3452 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/95">http://tools.ietf.org/wg/httpbis/trac/ticket/95</a>>: "Handling multiple Content-Length header s"3453 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/95">http://tools.ietf.org/wg/httpbis/trac/ticket/95</a>>: "Handling multiple Content-Length header fields" 3453 3454 </li> 3454 3455 </ul> … … 3462 3463 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/210">http://tools.ietf.org/wg/httpbis/trac/ticket/210</a>>: "define 'transparent' proxy" 3463 3464 </li> 3464 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/224">http://tools.ietf.org/wg/httpbis/trac/ticket/224</a>>: "Header Classification"3465 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/224">http://tools.ietf.org/wg/httpbis/trac/ticket/224</a>>: "Header Field Classification" 3465 3466 </li> 3466 3467 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/233">http://tools.ietf.org/wg/httpbis/trac/ticket/233</a>>: "Is * usable as a request-uri for new methods?" … … 3478 3479 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/53">http://tools.ietf.org/wg/httpbis/trac/ticket/53</a>>: "Allow is not in 13.5.2" 3479 3480 </li> 3480 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/95">http://tools.ietf.org/wg/httpbis/trac/ticket/95</a>>: "Handling multiple Content-Length header s"3481 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/95">http://tools.ietf.org/wg/httpbis/trac/ticket/95</a>>: "Handling multiple Content-Length header fields" 3481 3482 </li> 3482 3483 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/276">http://tools.ietf.org/wg/httpbis/trac/ticket/276</a>>: "untangle ABNFs for header fields" … … 3514 3515 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/186">http://tools.ietf.org/wg/httpbis/trac/ticket/186</a>>: "Document HTTP's error-handling philosophy" 3515 3516 </li> 3516 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/215">http://tools.ietf.org/wg/httpbis/trac/ticket/215</a>>: "Explain header registration"3517 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/215">http://tools.ietf.org/wg/httpbis/trac/ticket/215</a>>: "Explain header field registration" 3517 3518 </li> 3518 3519 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/219">http://tools.ietf.org/wg/httpbis/trac/ticket/219</a>>: "Revise Acknowledgements Sections"
Note: See TracChangeset
for help on using the changeset viewer.