Changeset 2591 for draft-ietf-httpbis


Ignore:
Timestamp:
28/01/14 00:12:23 (6 years ago)
Author:
fielding@…
Message:

(editorial) remove poorly worded requirements on persistent connections that are redundant to a carefully worded requirement above them; see #531

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

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.html

    r2590 r2591  
    21712171               <li>The connection will close after the current response.</li>
    21722172            </ul>
    2173             <p id="rfc.section.6.3.p.3">A server <em class="bcp14">MAY</em> assume that an HTTP/1.1 client intends to maintain a persistent connection until a <a href="#header.connection" class="smpl">close</a> connection option is received in a request.
    2174             </p>
    2175             <p id="rfc.section.6.3.p.4">A client <em class="bcp14">MAY</em> reuse a persistent connection until it sends or receives a <a href="#header.connection" class="smpl">close</a> connection option or receives an HTTP/1.0 response without a "keep-alive" connection option.
    2176             </p>
    2177             <p id="rfc.section.6.3.p.5">In order to remain persistent, all messages on a connection need to have a self-defined message length (i.e., one not defined
     2173            <p id="rfc.section.6.3.p.3">A client <em class="bcp14">MAY</em> send additional requests on a persistent connection until it sends or receives a <a href="#header.connection" class="smpl">close</a> connection option or receives an HTTP/1.0 response without a "keep-alive" connection option.
     2174            </p>
     2175            <p id="rfc.section.6.3.p.4">In order to remain persistent, all messages on a connection need to have a self-defined message length (i.e., one not defined
    21782176               by closure of the connection), as described in <a href="#message.body" title="Message Body">Section&nbsp;3.3</a>. A server <em class="bcp14">MUST</em> read the entire request message body or close the connection after sending its response, since otherwise the remaining data
    21792177               on a persistent connection would be misinterpreted as the next request. Likewise, a client <em class="bcp14">MUST</em> read the entire response message body if it intends to reuse the same connection for a subsequent request.
    21802178            </p>
    2181             <p id="rfc.section.6.3.p.6">A proxy server <em class="bcp14">MUST NOT</em> maintain a persistent connection with an HTTP/1.0 client (see <a href="http://tools.ietf.org/html/rfc2068#section-19.7.1">Section 19.7.1</a> of <a href="#RFC2068" id="rfc.xref.RFC2068.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a> for information and discussion of the problems with the Keep-Alive header field implemented by many HTTP/1.0 clients).
    2182             </p>
    2183             <p id="rfc.section.6.3.p.7">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&nbsp;A.1.2</a> for more information on backward compatibility with HTTP/1.0 clients.
     2179            <p id="rfc.section.6.3.p.5">A proxy server <em class="bcp14">MUST NOT</em> maintain a persistent connection with an HTTP/1.0 client (see <a href="http://tools.ietf.org/html/rfc2068#section-19.7.1">Section 19.7.1</a> of <a href="#RFC2068" id="rfc.xref.RFC2068.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a> for information and discussion of the problems with the Keep-Alive header field implemented by many HTTP/1.0 clients).
     2180            </p>
     2181            <p id="rfc.section.6.3.p.6">See <a href="#compatibility.with.http.1.0.persistent.connections" title="Keep-Alive Connections">Appendix&nbsp;A.1.2</a> for more information on backward compatibility with HTTP/1.0 clients.
    21842182            </p>
    21852183            <div id="persistent.retrying.requests">
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r2590 r2591  
    29652965</t>
    29662966<t>
    2967    A server &MAY; assume that an HTTP/1.1 client intends to maintain a
    2968    persistent connection until a <x:ref>close</x:ref> connection option
    2969    is received in a request.
    2970 </t>
    2971 <t>
    2972    A client &MAY; reuse a persistent connection until it sends or receives
    2973    a <x:ref>close</x:ref> connection option or receives an HTTP/1.0 response
    2974    without a "keep-alive" connection option.
     2967   A client &MAY; send additional requests on a persistent connection until it
     2968   sends or receives a <x:ref>close</x:ref> connection option or receives an
     2969   HTTP/1.0 response without a "keep-alive" connection option.
    29752970</t>
    29762971<t>
     
    29922987</t>
    29932988<t>
    2994    Clients and servers &SHOULD-NOT; assume that a persistent connection is
    2995    maintained for HTTP versions less than 1.1 unless it is explicitly
    2996    signaled.
    29972989   See <xref target="compatibility.with.http.1.0.persistent.connections"/>
    29982990   for more information on backward compatibility with HTTP/1.0 clients.
Note: See TracChangeset for help on using the changeset viewer.