Changeset 1705 for draft-ietf-httpbis/latest/p1-messaging.html
- Timestamp:
- 03/07/12 07:48:00 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r1704 r1705 2103 2103 </p> 2104 2104 <h4 id="rfc.section.6.3.2.1"><a href="#rfc.section.6.3.2.1">6.3.2.1</a> <a id="persistent.negotiation" href="#persistent.negotiation">Negotiation</a></h4> 2105 <p id="rfc.section.6.3.2.1.p.1">An HTTP/1.1 server <em class="bcp14">MAY</em> assume that a HTTP/1.1 client intends to maintain a persistent connection unless a Connection header field including the connection-token 2106 "close" was sent in the request. If the server chooses to close the connection immediately after sending the response, it <em class="bcp14">SHOULD</em> send a Connection header field including the connection-token "close". 2105 <p id="rfc.section.6.3.2.1.p.1">An HTTP/1.1 server <em class="bcp14">MAY</em> assume that a HTTP/1.1 client intends to maintain a persistent connection unless a Connection header field including the connection 2106 option "close" was sent in the request. If the server chooses to close the connection immediately after sending the response, 2107 it <em class="bcp14">SHOULD</em> send a Connection header field including the connection option "close". 2107 2108 </p> 2108 2109 <p id="rfc.section.6.3.2.1.p.2">An HTTP/1.1 client <em class="bcp14">MAY</em> expect a connection to remain open, but would decide to keep it open based on whether the response from a server contains 2109 a Connection header field with the connection -token close. In case the client does not want to maintain a connection for more2110 than that request, it <em class="bcp14">SHOULD</em> send a Connection header field including the connection-token close.2111 </p> 2112 <p id="rfc.section.6.3.2.1.p.3">If either the client or the server sends the close token in the Connection header field, that request becomes the last one2113 for the connection.2110 a Connection header field with the connection option "close". In case the client does not want to maintain a connection for 2111 more than that request, it <em class="bcp14">SHOULD</em> send a Connection header field including the connection option "close". 2112 </p> 2113 <p id="rfc.section.6.3.2.1.p.3">If either the client or the server sends the "close" option in the Connection header field, that request becomes the last 2114 one for the connection. 2114 2115 </p> 2115 2116 <p id="rfc.section.6.3.2.1.p.4">Clients and servers <em class="bcp14">SHOULD NOT</em> assume that a persistent connection is maintained for HTTP versions less than 1.1 unless it is explicitly signaled. See <a href="#compatibility.with.http.1.0.persistent.connections" title="Keep-Alive Connections">Appendix A.1.2</a> for more information on backward compatibility with HTTP/1.0 clients. … … 3000 3001 </p> 3001 3002 <p id="rfc.section.A.2.p.13">Change ABNF productions for header fields to only define the field value.</p> 3002 <p id="rfc.section.A.2.p.14">Clarify exactly when closeconnection options have to be sent. (<a href="#header.connection" id="rfc.xref.header.connection.11" title="Connection">Section 6.1</a>)3003 <p id="rfc.section.A.2.p.14">Clarify exactly when "close" connection options have to be sent. (<a href="#header.connection" id="rfc.xref.header.connection.11" title="Connection">Section 6.1</a>) 3003 3004 </p> 3004 3005 <p id="rfc.section.A.2.p.15">Define the semantics of the "Upgrade" header field in responses other than 101 (this was incorporated from <a href="#RFC2817" id="rfc.xref.RFC2817.3"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>). (<a href="#header.upgrade" id="rfc.xref.header.upgrade.2" title="Upgrade">Section 6.5</a>)
Note: See TracChangeset
for help on using the changeset viewer.