Ignore:
Timestamp:
Jul 21, 2011, 8:10:26 AM (8 years ago)
Author:
julian.reschke@…
Message:

IANA-reserve the header field name 'Close' (see #305)

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

Legend:

Unmodified
Added
Removed

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

    r1333 r1338  
    359359  }
    360360  @bottom-center {
    361        content: "Expires January 19, 2012";
     361       content: "Expires January 22, 2012";
    362362  }
    363363  @bottom-right {
    … …  
    410410      <meta name="dct.creator" content="Reschke, J. F.">
    411411      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest">
    412       <meta name="dct.issued" scheme="ISO8601" content="2011-07-18">
     412      <meta name="dct.issued" scheme="ISO8601" content="2011-07-21">
    413413      <meta name="dct.replaces" content="urn:ietf:rfc:2145">
    414414      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    … …  
    442442            </tr>
    443443            <tr>
    444                <td class="left">Expires: January 19, 2012</td>
     444               <td class="left">Expires: January 22, 2012</td>
    445445               <td class="right">HP</td>
    446446            </tr>
    … …  
    495495            <tr>
    496496               <td class="left"></td>
    497                <td class="right">July 18, 2011</td>
     497               <td class="right">July 21, 2011</td>
    498498            </tr>
    499499         </tbody>
    … …  
    525525         in progress”.
    526526      </p>
    527       <p>This Internet-Draft will expire on January 19, 2012.</p>
     527      <p>This Internet-Draft will expire on January 22, 2012.</p>
    528528      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    529529      <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    … …  
    24942494         </table>
    24952495      </div>
    2496       <p id="rfc.section.10.1.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
     2496      <p id="rfc.section.10.1.p.2">Furthermore, the header field name "Close" shall be registered as "reserved", as its use as HTTP header field would be in
     2497         conflict with the use of the "close" connection option for the "Connection" header field (<a href="#header.connection" id="rfc.xref.header.connection.10" title="Connection">Section&nbsp;9.1</a>).
     2498      </p>
     2499      <div id="rfc.table.u.2">
     2500         <table class="tt full left" cellpadding="3" cellspacing="0">
     2501            <thead>
     2502               <tr>
     2503                  <th>Header Field Name</th>
     2504                  <th>Protocol</th>
     2505                  <th>Status</th>
     2506                  <th>Reference</th>
     2507               </tr>
     2508            </thead>
     2509            <tbody>
     2510               <tr>
     2511                  <td class="left">Close</td>
     2512                  <td class="left">http</td>
     2513                  <td class="left">reserved</td>
     2514                  <td class="left"> <a href="#header.field.registration" title="Header Field Registration">Section&nbsp;10.1</a>
     2515                  </td>
     2516               </tr>
     2517            </tbody>
     2518         </table>
     2519      </div>
     2520      <p id="rfc.section.10.1.p.3">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
    24972521      <h2 id="rfc.section.10.2"><a href="#rfc.section.10.2">10.2</a>&nbsp;<a id="uri.scheme.registration" href="#uri.scheme.registration">URI Scheme Registration</a></h2>
    24982522      <p id="rfc.section.10.2.p.1">The entries for the "http" and "https" URI Schemes in the registry located at &lt;<a href="http://www.iana.org/assignments/uri-schemes.html">http://www.iana.org/assignments/uri-schemes.html</a>&gt; shall be updated to point to Sections <a href="#http.uri" title="http URI scheme">2.7.1</a> and <a href="#https.uri" title="https URI scheme">2.7.2</a> of this document (see <a href="#RFC4395" id="rfc.xref.RFC4395.1"><cite title="Guidelines and Registration Procedures for New URI Schemes">[RFC4395]</cite></a>).
    … …  
    26612685      <p id="rfc.section.10.5.p.2">The HTTP Status Code Registry located at &lt;<a href="http://www.iana.org/assignments/http-upgrade-tokens/">http://www.iana.org/assignments/http-upgrade-tokens/</a>&gt; shall be updated with the registration below:
    26622686      </p>
    2663       <div id="rfc.table.u.2">
     2687      <div id="rfc.table.u.3">
    26642688         <table class="tt full left" cellpadding="3" cellspacing="0">
    26652689            <thead>
    … …  
    30783102         Therefore, we need some other mechanism for indicating a persistent connection is desired, which is safe to use even when
    30793103         talking to an old proxy that ignores Connection. Persistent connections are the default for HTTP/1.1 messages; we introduce
    3080          a new keyword (Connection: close) for declaring non-persistence. See <a href="#header.connection" id="rfc.xref.header.connection.10" title="Connection">Section&nbsp;9.1</a>.
     3104         a new keyword (Connection: close) for declaring non-persistence. See <a href="#header.connection" id="rfc.xref.header.connection.11" title="Connection">Section&nbsp;9.1</a>.
    30813105      </p>
    30823106      <h2 id="rfc.section.B.2"><a href="#rfc.section.B.2">B.2</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2>
    … …  
    31073131      <p id="rfc.section.B.2.p.10">Change ABNF productions for header fields to only define the field value. (<a href="#header.field.definitions" title="Header Field Definitions">Section&nbsp;9</a>)
    31083132      </p>
    3109       <p id="rfc.section.B.2.p.11">Clarify exactly when close connection options must be sent. (<a href="#header.connection" id="rfc.xref.header.connection.11" title="Connection">Section&nbsp;9.1</a>)
     3133      <p id="rfc.section.B.2.p.11">Clarify exactly when close connection options must be sent. (<a href="#header.connection" id="rfc.xref.header.connection.12" title="Connection">Section&nbsp;9.1</a>)
    31103134      </p>
    31113135      <p id="rfc.section.B.2.p.12">Define the semantics of the "Upgrade" header field in responses other than 101 (this was incorporated from <a href="#RFC2817" id="rfc.xref.RFC2817.2"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>). (<a href="#header.upgrade" id="rfc.xref.header.upgrade.3" title="Upgrade">Section&nbsp;9.8</a>)
    … …  
    36303654      </ul>
    36313655      <h2 id="rfc.section.D.17"><a href="#rfc.section.D.17">D.17</a>&nbsp;<a id="changes.since.15" href="#changes.since.15">Since draft-ietf-httpbis-p1-messaging-15</a></h2>
    3632       <p id="rfc.section.D.17.p.1">None yet.</p>
     3656      <p id="rfc.section.D.17.p.1">Closed issues: </p>
     3657      <ul>
     3658         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/305">http://tools.ietf.org/wg/httpbis/trac/ticket/305</a>&gt;: "'Close' should be reserved in the HTTP header field registry"
     3659         </li>
     3660      </ul>
    36333661      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
    36343662      <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>
    … …  
    36653693                  <li>compress (Coding Format)&nbsp;&nbsp;<a href="#rfc.iref.c.8">6.2.2.1</a></li>
    36663694                  <li>connection&nbsp;&nbsp;<a href="#rfc.iref.c.2"><b>2.1</b></a></li>
    3667                   <li>Connection header field&nbsp;&nbsp;<a href="#rfc.xref.header.connection.1">2.4</a>, <a href="#rfc.xref.header.connection.2">2.6</a>, <a href="#rfc.xref.header.connection.3">3.4</a>, <a href="#rfc.xref.header.connection.4">7.1.2</a>, <a href="#rfc.xref.header.connection.5">7.1.3</a>, <a href="#rfc.xref.header.connection.6">7.1.3.1</a>, <a href="#rfc.iref.c.12"><b>9.1</b></a>, <a href="#rfc.xref.header.connection.7">9.5</a>, <a href="#rfc.xref.header.connection.8">9.8</a>, <a href="#rfc.xref.header.connection.9">10.1</a>, <a href="#rfc.xref.header.connection.10">B.1.2</a>, <a href="#rfc.xref.header.connection.11">B.2</a></li>
     3695                  <li>Connection header field&nbsp;&nbsp;<a href="#rfc.xref.header.connection.1">2.4</a>, <a href="#rfc.xref.header.connection.2">2.6</a>, <a href="#rfc.xref.header.connection.3">3.4</a>, <a href="#rfc.xref.header.connection.4">7.1.2</a>, <a href="#rfc.xref.header.connection.5">7.1.3</a>, <a href="#rfc.xref.header.connection.6">7.1.3.1</a>, <a href="#rfc.iref.c.12"><b>9.1</b></a>, <a href="#rfc.xref.header.connection.7">9.5</a>, <a href="#rfc.xref.header.connection.8">9.8</a>, <a href="#rfc.xref.header.connection.9">10.1</a>, <a href="#rfc.xref.header.connection.10">10.1</a>, <a href="#rfc.xref.header.connection.11">B.1.2</a>, <a href="#rfc.xref.header.connection.12">B.2</a></li>
    36683696                  <li>Content-Length header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-length.1">3.3</a>, <a href="#rfc.iref.c.13"><b>9.2</b></a>, <a href="#rfc.xref.header.content-length.2">10.1</a></li>
    36693697               </ul>
    … …  
    37983826                  <li>Header Fields&nbsp;&nbsp;
    37993827                     <ul>
    3800                         <li>Connection&nbsp;&nbsp;<a href="#rfc.xref.header.connection.1">2.4</a>, <a href="#rfc.xref.header.connection.2">2.6</a>, <a href="#rfc.xref.header.connection.3">3.4</a>, <a href="#rfc.xref.header.connection.4">7.1.2</a>, <a href="#rfc.xref.header.connection.5">7.1.3</a>, <a href="#rfc.xref.header.connection.6">7.1.3.1</a>, <a href="#rfc.iref.h.6"><b>9.1</b></a>, <a href="#rfc.xref.header.connection.7">9.5</a>, <a href="#rfc.xref.header.connection.8">9.8</a>, <a href="#rfc.xref.header.connection.9">10.1</a>, <a href="#rfc.xref.header.connection.10">B.1.2</a>, <a href="#rfc.xref.header.connection.11">B.2</a></li>
     3828                        <li>Connection&nbsp;&nbsp;<a href="#rfc.xref.header.connection.1">2.4</a>, <a href="#rfc.xref.header.connection.2">2.6</a>, <a href="#rfc.xref.header.connection.3">3.4</a>, <a href="#rfc.xref.header.connection.4">7.1.2</a>, <a href="#rfc.xref.header.connection.5">7.1.3</a>, <a href="#rfc.xref.header.connection.6">7.1.3.1</a>, <a href="#rfc.iref.h.6"><b>9.1</b></a>, <a href="#rfc.xref.header.connection.7">9.5</a>, <a href="#rfc.xref.header.connection.8">9.8</a>, <a href="#rfc.xref.header.connection.9">10.1</a>, <a href="#rfc.xref.header.connection.10">10.1</a>, <a href="#rfc.xref.header.connection.11">B.1.2</a>, <a href="#rfc.xref.header.connection.12">B.2</a></li>
    38013829                        <li>Content-Length&nbsp;&nbsp;<a href="#rfc.xref.header.content-length.1">3.3</a>, <a href="#rfc.iref.h.7"><b>9.2</b></a>, <a href="#rfc.xref.header.content-length.2">10.1</a></li>
    38023830                        <li>Date&nbsp;&nbsp;<a href="#rfc.xref.header.date.1">3.4</a>, <a href="#rfc.iref.h.8"><b>9.3</b></a>, <a href="#rfc.xref.header.date.2">10.1</a></li>

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

    r1337 r1338  
    37063706<?ENDINC p1-messaging.iana-headers ?>
    37073707<t>
     3708   Furthermore, the header field name "Close" shall be registered as "reserved", as its use as
     3709   HTTP header field would be in conflict with the use of the "close" connection
     3710   option for the "Connection" header field (<xref target="header.connection"/>).
     3711</t>
     3712<texttable align="left" suppress-title="true">
     3713   <ttcol>Header Field Name</ttcol>
     3714   <ttcol>Protocol</ttcol>
     3715   <ttcol>Status</ttcol>
     3716   <ttcol>Reference</ttcol>
     3717
     3718   <c>Close</c>
     3719   <c>http</c>
     3720   <c>reserved</c>
     3721   <c>
     3722      <xref target="header.field.registration"/>
     3723   </c>
     3724</texttable>
     3725<t>
    37083726   The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".
    37093727</t>
    … …  
    59966014<section title="Since draft-ietf-httpbis-p1-messaging-15" anchor="changes.since.15">
    59976015<t>
    5998   None yet.
     6016  Closed issues:
     6017  <list style="symbols">
     6018    <t>
     6019      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/305"/>:
     6020      "'Close' should be reserved in the HTTP header field registry"
     6021    </t>
     6022  </list>
    59996023</t>
    60006024</section>
Note: See TracChangeset for help on using the changeset viewer.