Changeset 1506


Ignore:
Timestamp:
Jan 14, 2012, 2:20:57 AM (8 years ago)
Author:
julian.reschke@…
Message:

improve index

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

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/extract-header-defs.xslt

    r1120 r1506  
    1616      <ttcol>Reference</ttcol>
    1717      <xsl:text>&#10;</xsl:text>
    18       <xsl:apply-templates select="//section[iref/@item='Header Fields']">
     18      <xsl:apply-templates select="//section[iref[@item='Header Fields' and @primary='true']]">
    1919        <xsl:sort select="iref[@item='Header Fields']/@subitem"/>
    2020      </xsl:apply-templates>
  • draft-ietf-httpbis/latest/p3-payload.html

    r1504 r1506  
    358358  }
    359359  @bottom-center {
    360        content: "Expires July 7, 2012";
     360       content: "Expires July 17, 2012";
    361361  }
    362362  @bottom-right {
     
    409409      <meta name="dct.creator" content="Reschke, J. F.">
    410410      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p3-payload-latest">
    411       <meta name="dct.issued" scheme="ISO8601" content="2012-01-04">
     411      <meta name="dct.issued" scheme="ISO8601" content="2012-01-14">
    412412      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    413413      <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.">
     
    435435            </tr>
    436436            <tr>
    437                <td class="left">Expires: July 7, 2012</td>
     437               <td class="left">Expires: July 17, 2012</td>
    438438               <td class="right">J. Mogul</td>
    439439            </tr>
     
    492492            <tr>
    493493               <td class="left"></td>
    494                <td class="right">January 4, 2012</td>
     494               <td class="right">January 14, 2012</td>
    495495            </tr>
    496496         </tbody>
     
    520520         in progress”.
    521521      </p>
    522       <p>This Internet-Draft will expire on July 7, 2012.</p>
     522      <p>This Internet-Draft will expire on July 17, 2012.</p>
    523523      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    524524      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    17151715         to perform a function equivalent to Content-Encoding. However, this parameter is not part of the MIME standards).
    17161716      </p>
     1717      <div id="rfc.iref.c.10"></div>
     1718      <div id="rfc.iref.h.10"></div>
    17171719      <h2 id="rfc.section.A.5"><a href="#rfc.section.A.5">A.5</a>&nbsp;<a id="no.content-transfer-encoding" href="#no.content-transfer-encoding">No Content-Transfer-Encoding</a></h2>
    17181720      <p id="rfc.section.A.5.p.1">HTTP does not use the Content-Transfer-Encoding field of MIME. Proxies and gateways from MIME-compliant protocols to HTTP <em class="bcp14">MUST</em> remove any Content-Transfer-Encoding prior to delivering the response message to an HTTP client.
     
    17571759      <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>)
    17581760      </p>
    1759       <p id="rfc.section.C.p.8">Remove reference to non-existant identity transfer-coding value tokens. (<a href="#no.content-transfer-encoding" title="No Content-Transfer-Encoding">Appendix&nbsp;A.5</a>)
     1761      <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>)
    17601762      </p>
    17611763      <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
     
    20742076                  <li>Content-Language header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-language.1">4.1</a>, <a href="#rfc.iref.c.7"><b>6.6</b></a>, <a href="#rfc.xref.header.content-language.2">7.1</a></li>
    20752077                  <li>Content-Location header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-location.1">4.1</a>, <a href="#rfc.iref.c.8"><b>6.7</b></a>, <a href="#rfc.xref.header.content-location.2">7.1</a>, <a href="#rfc.xref.header.content-location.3">C</a></li>
     2078                  <li>Content-Transfer-Encoding header field&nbsp;&nbsp;<a href="#rfc.iref.c.10">A.5</a>, <a href="#rfc.xref.no.content-transfer-encoding.1">C</a></li>
    20762079                  <li>Content-Type header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-type.1">2.3</a>, <a href="#rfc.xref.header.content-type.2">4.1</a>, <a href="#rfc.iref.c.9"><b>6.8</b></a>, <a href="#rfc.xref.header.content-type.3">7.1</a></li>
    20772080               </ul>
     
    21222125                        <li>Content-Language&nbsp;&nbsp;<a href="#rfc.xref.header.content-language.1">4.1</a>, <a href="#rfc.iref.h.6"><b>6.6</b></a>, <a href="#rfc.xref.header.content-language.2">7.1</a></li>
    21232126                        <li>Content-Location&nbsp;&nbsp;<a href="#rfc.xref.header.content-location.1">4.1</a>, <a href="#rfc.iref.h.7"><b>6.7</b></a>, <a href="#rfc.xref.header.content-location.2">7.1</a>, <a href="#rfc.xref.header.content-location.3">C</a></li>
     2127                        <li>Content-Transfer-Encoding&nbsp;&nbsp;<a href="#rfc.iref.h.10">A.5</a>, <a href="#rfc.xref.no.content-transfer-encoding.1">C</a></li>
    21242128                        <li>Content-Type&nbsp;&nbsp;<a href="#rfc.xref.header.content-type.1">2.3</a>, <a href="#rfc.xref.header.content-type.2">4.1</a>, <a href="#rfc.iref.h.8"><b>6.8</b></a>, <a href="#rfc.xref.header.content-type.3">7.1</a></li>
    21252129                        <li>MIME-Version&nbsp;&nbsp;<a href="#rfc.xref.mime-version.1">7.1</a>, <a href="#rfc.iref.h.9"><b>A.1</b></a></li>
  • draft-ietf-httpbis/latest/p3-payload.xml

    r1500 r1506  
    24602460
    24612461<section title="No Content-Transfer-Encoding" anchor="no.content-transfer-encoding">
     2462  <iref item="Content-Transfer-Encoding header field" x:for-anchor=""/>
     2463  <iref item="Header Fields" subitem="Content-Transfer-Encoding" x:for-anchor=""/>
    24622464<t>
    24632465   HTTP does not use the Content-Transfer-Encoding field of MIME.
Note: See TracChangeset for help on using the changeset viewer.