Ignore:
Timestamp:
03/02/14 05:03:28 (6 years ago)
Author:
fielding@…
Message:

(editorial) fix a very old xref bug, old terminology, and plural issue all in one sentence I have read a million times

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

Legend:

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

    r2614 r2615  
    448448  }
    449449  @bottom-center {
    450        content: "Expires August 5, 2014";
     450       content: "Expires August 6, 2014";
    451451  }
    452452  @bottom-right {
     
    490490      <meta name="dct.creator" content="Reschke, J. F.">
    491491      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest">
    492       <meta name="dct.issued" scheme="ISO8601" content="2014-02-01">
     492      <meta name="dct.issued" scheme="ISO8601" content="2014-02-02">
    493493      <meta name="dct.replaces" content="urn:ietf:rfc:2145">
    494494      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
     
    519519            <tr>
    520520               <td class="left">Intended status: Standards Track</td>
    521                <td class="right">February 1, 2014</td>
     521               <td class="right">February 2, 2014</td>
    522522            </tr>
    523523            <tr>
    524                <td class="left">Expires: August 5, 2014</td>
     524               <td class="left">Expires: August 6, 2014</td>
    525525               <td class="right"></td>
    526526            </tr>
     
    551551            in progress”.
    552552         </p>
    553          <p>This Internet-Draft will expire on August 5, 2014.</p>
     553         <p>This Internet-Draft will expire on August 6, 2014.</p>
    554554      </div>
    555555      <div id="rfc.copyrightnotice">
     
    29212921               that most implementations will choose substantially higher limits.
    29222922            </p>
    2923             <p id="rfc.section.9.3.p.3">A server can reject messages that have request-targets that are too long (<a href="p2-semantics.html#status.414" title="414 URI Too Long">Section 6.5.12</a> of <a href="#Part2" id="rfc.xref.Part2.35"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>) or request entities that are too large (<a href="p2-semantics.html#status.4xx" title="Client Error 4xx">Section 6.5</a> of <a href="#Part2" id="rfc.xref.Part2.36"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>). Additional status codes related to capacity limits have been defined by extensions to HTTP <a href="#RFC6585" id="rfc.xref.RFC6585.1"><cite title="Additional HTTP Status Codes">[RFC6585]</cite></a>.
     2923            <p id="rfc.section.9.3.p.3">A server can reject a message that has a request-target that is too long (<a href="p2-semantics.html#status.414" title="414 URI Too Long">Section 6.5.12</a> of <a href="#Part2" id="rfc.xref.Part2.35"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>) or a request payload that is too large (<a href="p2-semantics.html#status.413" title="413 Payload Too Large">Section 6.5.11</a> of <a href="#Part2" id="rfc.xref.Part2.36"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>). Additional status codes related to capacity limits have been defined by extensions to HTTP <a href="#RFC6585" id="rfc.xref.RFC6585.1"><cite title="Additional HTTP Status Codes">[RFC6585]</cite></a>.
    29242924            </p>
    29252925            <p id="rfc.section.9.3.p.4">Recipients ought to carefully limit the extent to which they process other protocol elements, including (but not limited to)
     
    37773777                        <li><em>Section 6.3.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.27">5.7.2</a></li>
    37783778                        <li><em>Section 6.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.32">6.7</a></li>
    3779                         <li><em>Section 6.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.36">9.3</a></li>
     3779                        <li><em>Section 6.5.11</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.36">9.3</a></li>
    37803780                        <li><em>Section 6.5.12</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.7">3.1.1</a>, <a href="#rfc.xref.Part2.35">9.3</a></li>
    37813781                        <li><em>Section 7.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.20">4.1.2</a></li>
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r2614 r2615  
    6161  <!ENTITY status-304             "<xref target='Part4' x:rel='#status.304' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    6262  <!ENTITY status-4xx             "<xref target='Part2' x:rel='#status.4xx' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     63  <!ENTITY status-413             "<xref target='Part2' x:rel='#status.413' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    6364  <!ENTITY status-414             "<xref target='Part2' x:rel='#status.414' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    6465  <!ENTITY iana-header-registry   "<xref target='Part2' x:rel='#header.field.registry' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     
    39983999</t>
    39994000<t>
    4000    A server can reject messages that
    4001    have request-targets that are too long (&status-414;) or request entities
    4002    that are too large (&status-4xx;). Additional status codes related to
     4001   A server can reject a message that
     4002   has a request-target that is too long (&status-414;) or a request payload
     4003   that is too large (&status-413;). Additional status codes related to
    40034004   capacity limits have been defined by extensions to HTTP
    40044005   <xref target="RFC6585"/>.
Note: See TracChangeset for help on using the changeset viewer.