Ignore:
Timestamp:
06/02/12 08:21:40 (9 years ago)
Author:
julian.reschke@…
Message:

Move text about closing connections on error from P2 to P1 (see #302)

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

Legend:

Unmodified
Added
Removed

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

    r1525 r1526  
    458458  }
    459459  @bottom-center {
    460        content: "Expires August 8, 2012";
     460       content: "Expires August 9, 2012";
    461461  }
    462462  @bottom-right {
    … …  
    508508      <meta name="dct.creator" content="Reschke, J. F.">
    509509      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest">
    510       <meta name="dct.issued" scheme="ISO8601" content="2012-02-05">
     510      <meta name="dct.issued" scheme="ISO8601" content="2012-02-06">
    511511      <meta name="dct.replaces" content="urn:ietf:rfc:2145">
    512512      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    … …  
    540540            </tr>
    541541            <tr>
    542                <td class="left">Expires: August 8, 2012</td>
     542               <td class="left">Expires: August 9, 2012</td>
    543543               <td class="right">HP</td>
    544544            </tr>
    … …  
    593593            <tr>
    594594               <td class="left"></td>
    595                <td class="right">February 5, 2012</td>
     595               <td class="right">February 6, 2012</td>
    596596            </tr>
    597597         </tbody>
    … …  
    626626         in progress”.
    627627      </p>
    628       <p>This Internet-Draft will expire on August 8, 2012.</p>
     628      <p>This Internet-Draft will expire on August 9, 2012.</p>
    629629      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    630630      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    … …  
    734734                     <li>6.2.2&nbsp;&nbsp;&nbsp;<a href="#persistent.monitor">Monitoring Connections for Error Status Messages</a></li>
    735735                     <li>6.2.3&nbsp;&nbsp;&nbsp;<a href="#use.of.the.100.status">Use of the 100 (Continue) Status</a></li>
     736                     <li>6.2.4&nbsp;&nbsp;&nbsp;<a href="#closing.connections.on.error">Closing Connections on Error</a></li>
    736737                  </ul>
    737738               </li>
    … …  
    20742075         </li>
    20752076      </ul>
     2077      <h3 id="rfc.section.6.2.4"><a href="#rfc.section.6.2.4">6.2.4</a>&nbsp;<a id="closing.connections.on.error" href="#closing.connections.on.error">Closing Connections on Error</a></h3>
     2078      <p id="rfc.section.6.2.4.p.1">If the client is sending data, a server implementation using TCP <em class="bcp14">SHOULD</em> be careful to ensure that the client acknowledges receipt of the packet(s) containing the response, before the server closes
     2079         the input connection. If the client continues sending data to the server after the close, the server's TCP stack will send
     2080         a reset packet to the client, which might erase the client's unacknowledged input buffers before they can be read and interpreted
     2081         by the HTTP application.
     2082      </p>
    20762083      <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="misc" href="#misc">Miscellaneous notes that might disappear</a></h1>
    20772084      <h2 id="rfc.section.7.1"><a href="#rfc.section.7.1">7.1</a>&nbsp;<a id="scheme.aliases" href="#scheme.aliases">Scheme aliases considered harmful</a></h2>
    … …  
    35903597      </ul>
    35913598      <h2 id="rfc.section.C.20"><a href="#rfc.section.C.20">C.20</a>&nbsp;<a id="changes.since.18" href="#changes.since.18">Since draft-ietf-httpbis-p1-messaging-18</a></h2>
    3592       <p id="rfc.section.C.20.p.1">None yet.</p>
     3599      <p id="rfc.section.C.20.p.1">Closed issues: </p>
     3600      <ul>
     3601         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/302">http://tools.ietf.org/wg/httpbis/trac/ticket/302</a>&gt;: "Misplaced text on connection handling in p2"
     3602         </li>
     3603      </ul>
    35933604      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
    35943605      <p class="noprint"><a href="#rfc.index.A">A</a> <a href="#rfc.index.B">B</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.D">D</a> <a href="#rfc.index.E">E</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.K">K</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.N">N</a> <a href="#rfc.index.O">O</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.T">T</a> <a href="#rfc.index.U">U</a> <a href="#rfc.index.V">V</a>

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

    r1525 r1526  
    28222822    </t>
    28232823  </list>
     2824</t>
     2825</section>
     2826
     2827<section title="Closing Connections on Error" anchor="closing.connections.on.error">
     2828<t>
     2829   If the client is sending data, a server implementation using TCP
     2830   &SHOULD; be careful to ensure that the client acknowledges receipt of
     2831   the packet(s) containing the response, before the server closes the
     2832   input connection. If the client continues sending data to the server
     2833   after the close, the server's TCP stack will send a reset packet to
     2834   the client, which might erase the client's unacknowledged input buffers
     2835   before they can be read and interpreted by the HTTP application.
    28242836</t>
    28252837</section>
    … …  
    59065918<section title="Since draft-ietf-httpbis-p1-messaging-18" anchor="changes.since.18">
    59075919<t>
    5908   None yet.
     5920  Closed issues:
     5921  <list style="symbols">
     5922    <t>
     5923      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/302"/>:
     5924      "Misplaced text on connection handling in p2"
     5925    </t>
     5926  </list>
    59095927</t>
    59105928</section>

  • draft-ietf-httpbis/latest/p2-semantics.html

    r1524 r1526  
    458458  }
    459459  @bottom-center {
    460        content: "Expires August 6, 2012";
     460       content: "Expires August 9, 2012";
    461461  }
    462462  @bottom-right {
    … …  
    510510      <meta name="dct.creator" content="Reschke, J. F.">
    511511      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
    512       <meta name="dct.issued" scheme="ISO8601" content="2012-02-03">
     512      <meta name="dct.issued" scheme="ISO8601" content="2012-02-06">
    513513      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    514514      <meta name="dct.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 2 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request header fields, response status codes, and response header fields.">
    … …  
    541541            </tr>
    542542            <tr>
    543                <td class="left">Expires: August 6, 2012</td>
     543               <td class="left">Expires: August 9, 2012</td>
    544544               <td class="right">HP</td>
    545545            </tr>
    … …  
    594594            <tr>
    595595               <td class="left"></td>
    596                <td class="right">February 3, 2012</td>
     596               <td class="right">February 6, 2012</td>
    597597            </tr>
    598598         </tbody>
    … …  
    624624         in progress”.
    625625      </p>
    626       <p>This Internet-Draft will expire on August 6, 2012.</p>
     626      <p>This Internet-Draft will expire on August 9, 2012.</p>
    627627      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    628628      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    … …  
    19821982         request, the server <em class="bcp14">SHOULD</em> include a representation containing an explanation of the error situation, and whether it is a temporary or permanent condition.
    19831983         These status codes are applicable to any request method. User agents <em class="bcp14">SHOULD</em> display any included representation to the user.
    1984       </p>
    1985       <p id="rfc.section.7.4.p.2">If the client is sending data, a server implementation using TCP <em class="bcp14">SHOULD</em> be careful to ensure that the client acknowledges receipt of the packet(s) containing the response, before the server closes
    1986          the input connection. If the client continues sending data to the server after the close, the server's TCP stack will send
    1987          a reset packet to the client, which might erase the client's unacknowledged input buffers before they can be read and interpreted
    1988          by the HTTP application.
    19891984      </p>
    19901985      <div id="rfc.iref.37"></div>
    … …  
    34993494      <p id="rfc.section.C.20.p.1">Closed issues: </p>
    35003495      <ul>
     3496         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/302">http://tools.ietf.org/wg/httpbis/trac/ticket/302</a>&gt;: "Misplaced text on connection handling in p2"
     3497         </li>
    35013498         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/332">http://tools.ietf.org/wg/httpbis/trac/ticket/332</a>&gt;: "relax requirements on hypertext in 3/4/5xx error responses"
    35023499         </li>

  • draft-ietf-httpbis/latest/p2-semantics.xml

    r1524 r1526  
    19071907   User agents &SHOULD; display any included representation to the user.
    19081908</t>
    1909 <t>
    1910    If the client is sending data, a server implementation using TCP
    1911    &SHOULD; be careful to ensure that the client acknowledges receipt of
    1912    the packet(s) containing the response, before the server closes the
    1913    input connection. If the client continues sending data to the server
    1914    after the close, the server's TCP stack will send a reset packet to
    1915    the client, which might erase the client's unacknowledged input buffers
    1916    before they can be read and interpreted by the HTTP application.
    1917 </t>
    19181909
    19191910<section title="400 Bad Request" anchor="status.400">
    … …  
    46824673  <list style="symbols">
    46834674    <t>
     4675      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/302"/>:
     4676      "Misplaced text on connection handling in p2"
     4677    </t>
     4678    <t>
    46844679      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/332"/>:
    46854680      "relax requirements on hypertext in 3/4/5xx error responses"
Note: See TracChangeset for help on using the changeset viewer.