Ignore:
Timestamp:
06/05/14 13:27:05 (6 years ago)
Author:
julian.reschke@…
Message:

"time-out" -> "timeout"/"time out" (#553)

File:
1 edited

Legend:

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

    r2641 r2642  
    677677               </li>
    678678               <li><a href="#rfc.section.6.4">6.4</a>&nbsp;&nbsp;&nbsp;<a href="#persistent.concurrency">Concurrency</a></li>
    679                <li><a href="#rfc.section.6.5">6.5</a>&nbsp;&nbsp;&nbsp;<a href="#persistent.failures">Failures and Time-outs</a></li>
     679               <li><a href="#rfc.section.6.5">6.5</a>&nbsp;&nbsp;&nbsp;<a href="#persistent.failures">Failures and Timeouts</a></li>
    680680               <li><a href="#rfc.section.6.6">6.6</a>&nbsp;&nbsp;&nbsp;<a href="#persistent.tear-down">Tear-down</a></li>
    681681               <li><a href="#rfc.section.6.7">6.7</a>&nbsp;&nbsp;&nbsp;<a href="#header.upgrade">Upgrade</a></li>
     
    16171617         <div id="incomplete.messages">
    16181618            <h2 id="rfc.section.3.4"><a href="#rfc.section.3.4">3.4</a>&nbsp;<a href="#incomplete.messages">Handling Incomplete Messages</a></h2>
    1619             <p id="rfc.section.3.4.p.1">A server that receives an incomplete request message, usually due to a canceled request or a triggered time-out exception, <em class="bcp14">MAY</em> send an error response prior to closing the connection.
     1619            <p id="rfc.section.3.4.p.1">A server that receives an incomplete request message, usually due to a canceled request or a triggered timeout exception, <em class="bcp14">MAY</em> send an error response prior to closing the connection.
    16201620            </p>
    16211621            <p id="rfc.section.3.4.p.2">A client that receives an incomplete response message, which can occur when a connection is closed prematurely or when decoding
     
    22662266         </div>
    22672267         <div id="persistent.failures">
    2268             <h2 id="rfc.section.6.5"><a href="#rfc.section.6.5">6.5</a>&nbsp;<a href="#persistent.failures">Failures and Time-outs</a></h2>
    2269             <p id="rfc.section.6.5.p.1">Servers will usually have some time-out value beyond which they will no longer maintain an inactive connection. Proxy servers
     2268            <h2 id="rfc.section.6.5"><a href="#rfc.section.6.5">6.5</a>&nbsp;<a href="#persistent.failures">Failures and Timeouts</a></h2>
     2269            <p id="rfc.section.6.5.p.1">Servers will usually have some timeout value beyond which they will no longer maintain an inactive connection. Proxy servers
    22702270               might make this a higher value since it is likely that the client will be making more connections through the same proxy server.
    2271                The use of persistent connections places no requirements on the length (or existence) of this time-out for either the client
     2271               The use of persistent connections places no requirements on the length (or existence) of this timeout for either the client
    22722272               or the server.
    22732273            </p>
    2274             <p id="rfc.section.6.5.p.2">A client or server that wishes to time-out <em class="bcp14">SHOULD</em> issue a graceful close on the connection. Implementations <em class="bcp14">SHOULD</em> constantly monitor open connections for a received closure signal and respond to it as appropriate, since prompt closure of
     2274            <p id="rfc.section.6.5.p.2">A client or server that wishes to time out <em class="bcp14">SHOULD</em> issue a graceful close on the connection. Implementations <em class="bcp14">SHOULD</em> constantly monitor open connections for a received closure signal and respond to it as appropriate, since prompt closure of
    22752275               both sides of a connection enables allocated system resources to be reclaimed.
    22762276            </p>
Note: See TracChangeset for help on using the changeset viewer.