Changeset 715 for draft-ietf-httpbis


Ignore:
Timestamp:
21/10/09 15:52:21 (11 years ago)
Author:
julian.reschke@…
Message:

Remove hard limit of two connections per server (see #131)

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

Legend:

Unmodified
Added
Removed

  • draft-ietf-httpbis/latest/p1-messaging.html

    r713 r715  
    400400      <meta name="DC.Creator" content="Reschke, J. F.">
    401401      <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest">
    402       <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-10-11">
     402      <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-10-21">
    403403      <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616">
    404404      <meta name="DC.Description.Abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 1 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 1 provides an overview of HTTP and its associated terminology, defines the &#34;http&#34; and &#34;https&#34; Uniform Resource Identifier (URI) schemes, defines the generic message syntax and parsing requirements for HTTP message frames, and describes general security concerns for implementations.">
    … …  
    437437         </tr>
    438438         <tr>
    439             <td class="header left">Expires: April 14, 2010</td>
     439            <td class="header left">Expires: April 24, 2010</td>
    440440            <td class="header right">H. Frystyk</td>
    441441         </tr>
    … …  
    486486         <tr>
    487487            <td class="header left"></td>
    488             <td class="header right">October 11, 2009</td>
     488            <td class="header right">October 21, 2009</td>
    489489         </tr>
    490490      </table>
    … …  
    510510      <p>The list of Internet-Draft Shadow Directories can be accessed at &lt;<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>&gt;.
    511511      </p>
    512       <p>This Internet-Draft will expire in April 14, 2010.</p>
     512      <p>This Internet-Draft will expire in April 24, 2010.</p>
    513513      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    514514      <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    … …  
    17061706      <p id="rfc.section.7.1.4.p.5">Servers <em class="bcp14">SHOULD</em> always respond to at least one request per connection, if at all possible. Servers <em class="bcp14">SHOULD NOT</em> close a connection in the middle of transmitting a response, unless a network or client failure is suspected.
    17071707      </p>
    1708       <p id="rfc.section.7.1.4.p.6">Clients that use persistent connections <em class="bcp14">SHOULD</em> limit the number of simultaneous connections that they maintain to a given server. A single-user client <em class="bcp14">SHOULD NOT</em> maintain more than 2 connections with any server or proxy. A proxy <em class="bcp14">SHOULD</em> use up to 2*N connections to another server or proxy, where N is the number of simultaneously active users. These guidelines
    1709          are intended to improve HTTP response times and avoid congestion.
    1710       </p>
     1708      <p id="rfc.section.7.1.4.p.6">Clients (including proxies) <em class="bcp14">SHOULD</em> limit the number of simultaneous connections that they maintain to a given server (including proxies).
     1709      </p>
     1710      <p id="rfc.section.7.1.4.p.7">Previous revisions of HTTP gave a specific number of connections as a ceiling, but this was found to be impractical for many
     1711         applications. As a result, this specification does not mandate a particular maximum number of connections, but instead encourages
     1712         clients to be conservative when opening multiple connections.
     1713      </p>
     1714      <p id="rfc.section.7.1.4.p.8">In particular, while using multiple connections avoids the "head-of-line blocking" problem (whereby a request that takes significant
     1715         server-side processing and/or has a large payload can block subsequent requests on the same connection), each connection used
     1716         consumes server resources (sometimes significantly), and furthermore using multiple connections can cause undesirable side
     1717         effects in congested networks.
     1718      </p>
     1719      <p id="rfc.section.7.1.4.p.9">Note that servers might reject traffic that they deem abusive, including an excessive number of connections from a client.</p>
    17111720      <h2 id="rfc.section.7.2"><a href="#rfc.section.7.2">7.2</a>&nbsp;<a id="message.transmission.requirements" href="#message.transmission.requirements">Message Transmission Requirements</a></h2>
    17121721      <h3 id="rfc.section.7.2.1"><a href="#rfc.section.7.2.1">7.2.1</a>&nbsp;<a id="persistent.flow" href="#persistent.flow">Persistent Connections and Flow Control</a></h3>
    … …  
    28212830         disallowed line folding in chunk extensions. (<a href="#chunked.encoding" title="Chunked Transfer Coding">Section&nbsp;6.2.1</a>)
    28222831      </p>
    2823       <p id="rfc.section.B.4.p.8">Clarify exactly when close connection options must be sent. (<a href="#header.connection" id="rfc.xref.header.connection.8" title="Connection">Section&nbsp;9.1</a>)
     2832      <p id="rfc.section.B.4.p.8">Remove hard limit of two connections per server. (<a href="#persistent.practical" title="Practical Considerations">Section&nbsp;7.1.4</a>)
     2833      </p>
     2834      <p id="rfc.section.B.4.p.9">Clarify exactly when close connection options must be sent. (<a href="#header.connection" id="rfc.xref.header.connection.8" title="Connection">Section&nbsp;9.1</a>)
    28242835      </p>
    28252836      <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
    … …  
    32203231      <ul>
    32213232         <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"
     3233         </li>
     3234         <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"
    32223235         </li>
    32233236         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/157">http://tools.ietf.org/wg/httpbis/trac/ticket/157</a>&gt;: "IP addresses in URLs"

  • draft-ietf-httpbis/latest/p1-messaging.xml

    r713 r715  
    22602260</t>
    22612261<t>
    2262    Clients that use persistent connections &SHOULD; limit the number of
    2263    simultaneous connections that they maintain to a given server. A
    2264    single-user client &SHOULD-NOT; maintain more than 2 connections with
    2265    any server or proxy. A proxy &SHOULD; use up to 2*N connections to
    2266    another server or proxy, where N is the number of simultaneously
    2267    active users. These guidelines are intended to improve HTTP response
    2268    times and avoid congestion.
     2262   Clients (including proxies) &SHOULD; limit the number of simultaneous
     2263   connections that they maintain to a given server (including proxies).
     2264</t>
     2265<t>
     2266   Previous revisions of HTTP gave a specific number of connections as a
     2267   ceiling, but this was found to be impractical for many applications. As a
     2268   result, this specification does not mandate a particular maximum number of
     2269   connections, but instead encourages clients to be conservative when opening
     2270   multiple connections.
     2271</t>
     2272<t>
     2273   In particular, while using multiple connections avoids the "head-of-line
     2274   blocking" problem (whereby a request that takes significant server-side
     2275   processing and/or has a large payload can block subsequent requests on the
     2276   same connection), each connection used consumes server resources (sometimes
     2277   significantly), and furthermore using multiple connections can cause
     2278   undesirable side effects in congested networks.
     2279</t>
     2280<t>
     2281   Note that servers might reject traffic that they deem abusive, including an
     2282   excessive number of connections from a client.
    22692283</t>
    22702284</section>
    … …  
    46354649</t>
    46364650<t>
     4651  Remove hard limit of two connections per server.
     4652  (<xref target="persistent.practical"/>)
     4653</t>
     4654<t>
    46374655  Clarify exactly when close connection options must be sent.
    46384656  (<xref target="header.connection"/>)
    … …  
    52495267    </t>
    52505268    <t>
     5269      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/131"/>:
     5270      "increase connection limit"
     5271    </t>
     5272    <t>
    52515273      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/157"/>:
    52525274      "IP addresses in URLs"
Note: See TracChangeset for help on using the changeset viewer.