Changeset 1566


Ignore:
Timestamp:
Mar 7, 2012, 4:57:38 AM (7 years ago)
Author:
julian.reschke@…
Message:

Sort "Changes from RFC 2616" sections; remove unused Section wrapper (editorial)

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

Legend:

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

    r1565 r1566  
    30673067      </p>
    30683068      <h2 id="rfc.section.A.2"><a href="#rfc.section.A.2">A.2</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2>
    3069       <p id="rfc.section.A.2.p.1">Empty list elements in list productions have been deprecated. (<a href="#abnf.extension" title="ABNF list extension: #rule">Section&nbsp;3.2.5</a>)
    3070       </p>
    3071       <p id="rfc.section.A.2.p.2">Rules about implicit linear whitespace between certain grammar productions have been removed; now whitespace is only allowed
     3069      <p id="rfc.section.A.2.p.1">Clarify that the string "HTTP" in the HTTP-version ABFN production is case sensitive. Restrict the version numbers to be single
     3070         digits due to the fact that implementations are known to handle multi-digit version numbers incorrectly. (<a href="#http.version" title="Protocol Versioning">Section&nbsp;2.6</a>)
     3071      </p>
     3072      <p id="rfc.section.A.2.p.2">Update use of abs_path production from RFC 1808 to the path-absolute + query components of RFC 3986. State that the asterisk
     3073         form is allowed for the OPTIONS request method only. (<a href="#request-target" title="request-target">Section&nbsp;3.1.1.2</a>)
     3074      </p>
     3075      <p id="rfc.section.A.2.p.3">Require that invalid whitespace around field-names be rejected. (<a href="#header.fields" title="Header Fields">Section&nbsp;3.2</a>)
     3076      </p>
     3077      <p id="rfc.section.A.2.p.4">Rules about implicit linear whitespace between certain grammar productions have been removed; now whitespace is only allowed
    30723078         where specifically defined in the ABNF. (<a href="#whitespace" title="Whitespace">Section&nbsp;3.2.1</a>)
    3073       </p>
    3074       <p id="rfc.section.A.2.p.3">Clarify that the string "HTTP" in the HTTP-version ABFN production is case sensitive. Restrict the version numbers to be single
    3075          digits due to the fact that implementations are known to handle multi-digit version numbers incorrectly. (<a href="#http.version" title="Protocol Versioning">Section&nbsp;2.6</a>)
    3076       </p>
    3077       <p id="rfc.section.A.2.p.4">Require that invalid whitespace around field-names be rejected. (<a href="#header.fields" title="Header Fields">Section&nbsp;3.2</a>)
    30783079      </p>
    30793080      <p id="rfc.section.A.2.p.5">The NUL octet is no longer allowed in comment and quoted-string text. The quoted-pair rule no longer allows escaping control
     
    30813082         rule was removed). (<a href="#field.components" title="Field value components">Section&nbsp;3.2.4</a>)
    30823083      </p>
    3083       <p id="rfc.section.A.2.p.6">Require recipients to handle bogus Content-Length header fields as errors. (<a href="#message.body" title="Message Body">Section&nbsp;3.3</a>)
    3084       </p>
    3085       <p id="rfc.section.A.2.p.7">Remove reference to non-existent identity transfer-coding value tokens. (Sections <a href="#message.body" title="Message Body">3.3</a> and <a href="#transfer.codings" title="Transfer Codings">5</a>)
    3086       </p>
    3087       <p id="rfc.section.A.2.p.8">Update use of abs_path production from RFC 1808 to the path-absolute + query components of RFC 3986. State that the asterisk
    3088          form is allowed for the OPTIONS request method only. (<a href="#request-target" title="request-target">Section&nbsp;3.1.1.2</a>)
     3084      <p id="rfc.section.A.2.p.6">Empty list elements in list productions have been deprecated. (<a href="#abnf.extension" title="ABNF list extension: #rule">Section&nbsp;3.2.5</a>)
     3085      </p>
     3086      <p id="rfc.section.A.2.p.7">Require recipients to handle bogus Content-Length header fields as errors. (<a href="#message.body" title="Message Body">Section&nbsp;3.3</a>)
     3087      </p>
     3088      <p id="rfc.section.A.2.p.8">Remove reference to non-existent identity transfer-coding value tokens. (Sections <a href="#message.body" title="Message Body">3.3</a> and <a href="#transfer.codings" title="Transfer Codings">5</a>)
    30893089      </p>
    30903090      <p id="rfc.section.A.2.p.9">Clarification that the chunk length does not include the count of the octets in the chunk header and trailer. Furthermore
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r1565 r1566  
    49584958<section title="Changes from RFC 2616" anchor="changes.from.rfc.2616">
    49594959<t>
    4960   Empty list elements in list productions have been deprecated.
    4961   (<xref target="abnf.extension"/>)
    4962 </t>
    4963 <t>
    4964   Rules about implicit linear whitespace between certain grammar productions
    4965   have been removed; now whitespace is only allowed where specifically
    4966   defined in the ABNF.
    4967   (<xref target="whitespace"/>)
    4968 </t>
    4969 <t>
    49704960  Clarify that the string "HTTP" in the HTTP-version ABFN production is case
    49714961  sensitive. Restrict the version numbers to be single digits due to the fact
     
    49754965</t>
    49764966<t>
     4967  Update use of abs_path production from RFC 1808 to the path-absolute + query
     4968  components of RFC 3986. State that the asterisk form is allowed for the OPTIONS
     4969  request method only.
     4970  (<xref target="request-target"/>)
     4971</t>
     4972<t>
    49774973  Require that invalid whitespace around field-names be rejected.
    49784974  (<xref target="header.fields"/>)
     4975</t>
     4976<t>
     4977  Rules about implicit linear whitespace between certain grammar productions
     4978  have been removed; now whitespace is only allowed where specifically
     4979  defined in the ABNF.
     4980  (<xref target="whitespace"/>)
    49794981</t>
    49804982<t> 
     
    49864988</t>
    49874989<t>
     4990  Empty list elements in list productions have been deprecated.
     4991  (<xref target="abnf.extension"/>)
     4992</t>
     4993<t>
    49884994  Require recipients to handle bogus Content-Length header fields as errors.
    49894995  (<xref target="message.body"/>)
     
    49934999  (Sections <xref format="counter" target="message.body"/> and
    49945000  <xref format="counter" target="transfer.codings"/>)
    4995 </t>
    4996 <t>
    4997   Update use of abs_path production from RFC 1808 to the path-absolute + query
    4998   components of RFC 3986. State that the asterisk form is allowed for the OPTIONS
    4999   request method only.
    5000   (<xref target="request-target"/>)
    50015001</t>
    50025002<t>
  • draft-ietf-httpbis/latest/p3-payload.html

    r1555 r1566  
    460460  }
    461461  @bottom-center {
    462        content: "Expires September 4, 2012";
     462       content: "Expires September 8, 2012";
    463463  }
    464464  @bottom-right {
     
    511511      <meta name="dct.creator" content="Reschke, J. F.">
    512512      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p3-payload-latest">
    513       <meta name="dct.issued" scheme="ISO8601" content="2012-03-03">
     513      <meta name="dct.issued" scheme="ISO8601" content="2012-03-07">
    514514      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    515515      <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 3 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 3 defines HTTP message content, metadata, and content negotiation.">
     
    537537            </tr>
    538538            <tr>
    539                <td class="left">Expires: September 4, 2012</td>
     539               <td class="left">Expires: September 8, 2012</td>
    540540               <td class="right">J. Mogul</td>
    541541            </tr>
     
    594594            <tr>
    595595               <td class="left"></td>
    596                <td class="right">March 3, 2012</td>
     596               <td class="right">March 7, 2012</td>
    597597            </tr>
    598598         </tbody>
     
    622622         in progress”.
    623623      </p>
    624       <p>This Internet-Draft will expire on September 4, 2012.</p>
     624      <p>This Internet-Draft will expire on September 8, 2012.</p>
    625625      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    626626      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    18601860         relative links in content-negotiated resources. (<a href="#header.content-location" id="rfc.xref.header.content-location.3" title="Content-Location">Section&nbsp;6.7</a>)
    18611861      </p>
    1862       <p id="rfc.section.C.p.7">Remove discussion of Content-Disposition header field, it is now defined by <a href="#RFC6266" id="rfc.xref.RFC6266.2"><cite title="Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)">[RFC6266]</cite></a>. (<a href="#additional.features" title="Additional Features">Appendix&nbsp;B</a>)
    1863       </p>
    1864       <p id="rfc.section.C.p.8">Remove reference to non-existant identity transfer-coding value tokens. (<a href="#no.content-transfer-encoding" id="rfc.xref.no.content-transfer-encoding.1" title="No Content-Transfer-Encoding">Appendix&nbsp;A.5</a>)
     1862      <p id="rfc.section.C.p.7">Remove reference to non-existant identity transfer-coding value tokens. (<a href="#no.content-transfer-encoding" id="rfc.xref.no.content-transfer-encoding.1" title="No Content-Transfer-Encoding">Appendix&nbsp;A.5</a>)
     1863      </p>
     1864      <p id="rfc.section.C.p.8">Remove discussion of Content-Disposition header field, it is now defined by <a href="#RFC6266" id="rfc.xref.RFC6266.2"><cite title="Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)">[RFC6266]</cite></a>. (<a href="#additional.features" title="Additional Features">Appendix&nbsp;B</a>)
    18651865      </p>
    18661866      <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
  • draft-ietf-httpbis/latest/p3-payload.xml

    r1552 r1566  
    25522552</t>
    25532553<t>
     2554  Remove reference to non-existant identity transfer-coding value tokens.
     2555  (<xref target="no.content-transfer-encoding"/>)
     2556</t>
     2557<t>
    25542558  Remove discussion of Content-Disposition header field, it is now defined
    25552559  by <xref target="RFC6266"/>.
    25562560  (<xref target="additional.features"/>)
    2557 </t>
    2558 <t>
    2559   Remove reference to non-existant identity transfer-coding value tokens.
    2560   (<xref target="no.content-transfer-encoding"/>)
    25612561</t>
    25622562</section>
  • draft-ietf-httpbis/latest/p5-range.html

    r1555 r1566  
    460460  }
    461461  @bottom-center {
    462        content: "Expires September 4, 2012";
     462       content: "Expires September 8, 2012";
    463463  }
    464464  @bottom-right {
     
    492492      <link rel="Chapter" href="#rfc.section.9" title="9 References">
    493493      <link rel="Appendix" title="A Internet Media Type multipart/byteranges" href="#rfc.section.A">
    494       <link rel="Appendix" title="B Compatibility with Previous Versions" href="#rfc.section.B">
     494      <link rel="Appendix" title="B Changes from RFC 2616" href="#rfc.section.B">
    495495      <link rel="Appendix" title="C Collected ABNF" href="#rfc.section.C">
    496496      <link rel="Appendix" title="D Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.D">
     
    509509      <meta name="dct.creator" content="Reschke, J. F.">
    510510      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest">
    511       <meta name="dct.issued" scheme="ISO8601" content="2012-03-03">
     511      <meta name="dct.issued" scheme="ISO8601" content="2012-03-07">
    512512      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    513513      <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 5 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 5 defines range-specific requests and the rules for constructing and combining responses to those requests.">
     
    535535            </tr>
    536536            <tr>
    537                <td class="left">Expires: September 4, 2012</td>
     537               <td class="left">Expires: September 8, 2012</td>
    538538               <td class="right">J. Mogul</td>
    539539            </tr>
     
    592592            <tr>
    593593               <td class="left"></td>
    594                <td class="right">March 3, 2012</td>
     594               <td class="right">March 7, 2012</td>
    595595            </tr>
    596596         </tbody>
     
    620620         in progress”.
    621621      </p>
    622       <p>This Internet-Draft will expire on September 4, 2012.</p>
     622      <p>This Internet-Draft will expire on September 8, 2012.</p>
    623623      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    624624      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    690690         <li><a href="#rfc.authors">Authors' Addresses</a></li>
    691691         <li>A.&nbsp;&nbsp;&nbsp;<a href="#internet.media.type.multipart.byteranges">Internet Media Type multipart/byteranges</a></li>
    692          <li>B.&nbsp;&nbsp;&nbsp;<a href="#compatibility">Compatibility with Previous Versions</a><ul>
    693                <li>B.1&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
    694             </ul>
    695          </li>
     692         <li>B.&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
    696693         <li>C.&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
    697694         <li>D.&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul>
     
    13591356         </li>
    13601357      </ol>
    1361       <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="compatibility" href="#compatibility">Compatibility with Previous Versions</a></h1>
    1362       <h2 id="rfc.section.B.1"><a href="#rfc.section.B.1">B.1</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2>
    1363       <p id="rfc.section.B.1.p.1">Clarify that it is not ok to use a weak validator in a 206 response. (<a href="#status.206" id="rfc.xref.status.206.2" title="206 Partial Content">Section&nbsp;3.1</a>)
    1364       </p>
    1365       <p id="rfc.section.B.1.p.2">Change ABNF productions for header fields to only define the field value. (<a href="#header.field.definitions" title="Header Field Definitions">Section&nbsp;5</a>)
    1366       </p>
    1367       <p id="rfc.section.B.1.p.3">Clarify that multipart/byteranges can consist of a single part. (<a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>)
     1358      <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h1>
     1359      <p id="rfc.section.B.p.1">Clarify that it is not ok to use a weak validator in a 206 response. (<a href="#status.206" id="rfc.xref.status.206.2" title="206 Partial Content">Section&nbsp;3.1</a>)
     1360      </p>
     1361      <p id="rfc.section.B.p.2">Change ABNF productions for header fields to only define the field value. (<a href="#header.field.definitions" title="Header Field Definitions">Section&nbsp;5</a>)
     1362      </p>
     1363      <p id="rfc.section.B.p.3">Clarify that multipart/byteranges can consist of a single part. (<a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>)
    13681364      </p>
    13691365      <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
     
    15691565         <ul class="ind">
    15701566            <li><a id="rfc.index.2" href="#rfc.index.2"><b>2</b></a><ul>
    1571                   <li>206 Partial Content (status code)&nbsp;&nbsp;<a href="#rfc.iref.3"><b>3.1</b></a>, <a href="#rfc.xref.status.206.1">6.1</a>, <a href="#rfc.xref.status.206.2">B.1</a></li>
     1567                  <li>206 Partial Content (status code)&nbsp;&nbsp;<a href="#rfc.iref.3"><b>3.1</b></a>, <a href="#rfc.xref.status.206.1">6.1</a>, <a href="#rfc.xref.status.206.2">B</a></li>
    15721568               </ul>
    15731569            </li>
     
    16831679                  <li>Status Codes&nbsp;&nbsp;
    16841680                     <ul>
    1685                         <li>206 Partial Content&nbsp;&nbsp;<a href="#rfc.iref.s.1"><b>3.1</b></a>, <a href="#rfc.xref.status.206.1">6.1</a>, <a href="#rfc.xref.status.206.2">B.1</a></li>
     1681                        <li>206 Partial Content&nbsp;&nbsp;<a href="#rfc.iref.s.1"><b>3.1</b></a>, <a href="#rfc.xref.status.206.1">6.1</a>, <a href="#rfc.xref.status.206.2">B</a></li>
    16861682                        <li>416 Requested Range Not Satisfiable&nbsp;&nbsp;<a href="#rfc.iref.s.2"><b>3.2</b></a>, <a href="#rfc.xref.status.416.1">6.1</a></li>
    16871683                     </ul>
  • draft-ietf-httpbis/latest/p5-range.xml

    r1552 r1566  
    15311531</section>
    15321532
    1533 <section title="Compatibility with Previous Versions" anchor="compatibility">
    15341533<section title="Changes from RFC 2616" anchor="changes.from.rfc.2616">
    15351534<t>
     
    15451544  (<xref target="internet.media.type.multipart.byteranges"/>)
    15461545</t>
    1547 </section>
    1548 
    15491546</section>
    15501547
Note: See TracChangeset for help on using the changeset viewer.