Ignore:
Timestamp:
Jul 3, 2012, 12:48:00 AM (7 years ago)
Author:
julian.reschke@…
Message:

Avoid use of "connection-token" outside the header field definition; use "connection option" instead; consistently quote the "close" connection option.

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

Legend:

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

    r1704 r1705  
    21032103      </p>
    21042104      <h4 id="rfc.section.6.3.2.1"><a href="#rfc.section.6.3.2.1">6.3.2.1</a>&nbsp;<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".
    21072108      </p>
    21082109      <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 more
    2110          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 one
    2113          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.
    21142115      </p>
    21152116      <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&nbsp;A.1.2</a> for more information on backward compatibility with HTTP/1.0 clients.
     
    30003001      </p>
    30013002      <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 close connection options have to be sent. (<a href="#header.connection" id="rfc.xref.header.connection.11" title="Connection">Section&nbsp;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&nbsp;6.1</a>)
    30033004      </p>
    30043005      <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&nbsp;6.5</a>)
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r1704 r1705  
    29262926   An HTTP/1.1 server &MAY; assume that a HTTP/1.1 client intends to
    29272927   maintain a persistent connection unless a Connection header field including
    2928    the connection-token "close" was sent in the request. If the server
     2928   the connection option "close" was sent in the request. If the server
    29292929   chooses to close the connection immediately after sending the
    29302930   response, it &SHOULD; send a Connection header field including the
    2931    connection-token "close".
     2931   connection option "close".
    29322932</t>
    29332933<t>
    29342934   An HTTP/1.1 client &MAY; expect a connection to remain open, but would
    29352935   decide to keep it open based on whether the response from a server
    2936    contains a Connection header field with the connection-token close. In case
     2936   contains a Connection header field with the connection option "close". In case
    29372937   the client does not want to maintain a connection for more than that
    29382938   request, it &SHOULD; send a Connection header field including the
    2939    connection-token close.
    2940 </t>
    2941 <t>
    2942    If either the client or the server sends the close token in the
     2939   connection option "close".
     2940</t>
     2941<t>
     2942   If either the client or the server sends the "close" option in the
    29432943   Connection header field, that request becomes the last one for the
    29442944   connection.
     
    48854885</t>
    48864886<t>
    4887   Clarify exactly when close connection options have to be sent.
     4887  Clarify exactly when "close" connection options have to be sent.
    48884888  (<xref target="header.connection"/>)
    48894889</t>
Note: See TracChangeset for help on using the changeset viewer.