Ignore:
Timestamp:
Jun 10, 2011, 12:24:02 AM (9 years ago)
Author:
julian.reschke@…
Message:

draft-ietf-httpbis-content-disp -> RFC6266 (see #123)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p3-payload.html

    r1303 r1307  
    359359  }
    360360  @bottom-center {
    361        content: "Expires December 3, 2011";
     361       content: "Expires December 12, 2011";
    362362  }
    363363  @bottom-right {
     
    408408      <meta name="dct.creator" content="Reschke, J. F.">
    409409      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p3-payload-latest">
    410       <meta name="dct.issued" scheme="ISO8601" content="2011-06-01">
     410      <meta name="dct.issued" scheme="ISO8601" content="2011-06-10">
    411411      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    412412      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia 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.">
     
    434434            </tr>
    435435            <tr>
    436                <td class="left">Expires: December 3, 2011</td>
     436               <td class="left">Expires: December 12, 2011</td>
    437437               <td class="right">J. Mogul</td>
    438438            </tr>
     
    491491            <tr>
    492492               <td class="left"></td>
    493                <td class="right">June 1, 2011</td>
     493               <td class="right">June 10, 2011</td>
    494494            </tr>
    495495         </tbody>
     
    519519         in progress”.
    520520      </p>
    521       <p>This Internet-Draft will expire on December 3, 2011.</p>
     521      <p>This Internet-Draft will expire on December 12, 2011.</p>
    522522      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    523523      <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    16391639         </tr>
    16401640         <tr>
    1641             <td class="reference"><b id="draft-ietf-httpbis-content-disp">[draft-ietf-httpbis-content-disp]</b></td>
    1642             <td class="top"><a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">Reschke, J.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-content-disp-09">Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-content-disp-09 (work in progress), March&nbsp;2011.
     1641            <td class="reference"><b id="RFC6266">[RFC6266]</b></td>
     1642            <td class="top"><a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">Reschke, J.</a>, “<a href="http://tools.ietf.org/html/rfc6266">Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)</a>”, RFC&nbsp;6266, June&nbsp;2011.
    16431643            </td>
    16441644         </tr>
     
    17251725         experimental deployment found lacking that are now addressed in the base HTTP/1.1 specification.
    17261726      </p>
    1727       <p id="rfc.section.B.p.2">A number of other header fields, such as Content-Disposition and Title, from SMTP and MIME are also often implemented (see <a href="#draft-ietf-httpbis-content-disp" id="rfc.xref.draft-ietf-httpbis-content-disp.1"><cite title="Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)">[draft-ietf-httpbis-content-disp]</cite></a> and <a href="#RFC2076" id="rfc.xref.RFC2076.1"><cite title="Common Internet Message Headers">[RFC2076]</cite></a>).
     1727      <p id="rfc.section.B.p.2">A number of other header fields, such as Content-Disposition and Title, from SMTP and MIME are also often implemented (see <a href="#RFC6266" id="rfc.xref.RFC6266.1"><cite title="Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)">[RFC6266]</cite></a> and <a href="#RFC2076" id="rfc.xref.RFC2076.1"><cite title="Common Internet Message Headers">[RFC2076]</cite></a>).
    17281728      </p>
    17291729      <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h1>
     
    17431743         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>)
    17441744      </p>
    1745       <p id="rfc.section.C.p.7">Remove discussion of Content-Disposition header field, it is now defined by <a href="#draft-ietf-httpbis-content-disp" id="rfc.xref.draft-ietf-httpbis-content-disp.2"><cite title="Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)">[draft-ietf-httpbis-content-disp]</cite></a>. (<a href="#additional.features" title="Additional Features">Appendix&nbsp;B</a>)
     1745      <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>)
    17461746      </p>
    17471747      <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>)
     
    20522052            <li><a id="rfc.index.D" href="#rfc.index.D"><b>D</b></a><ul>
    20532053                  <li>deflate (Coding Format)&nbsp;&nbsp;<a href="#rfc.iref.d.1">2.2</a></li>
    2054                   <li><em>draft-ietf-httpbis-content-disp</em>&nbsp;&nbsp;<a href="#draft-ietf-httpbis-content-disp"><b>10.2</b></a>, <a href="#rfc.xref.draft-ietf-httpbis-content-disp.1">B</a>, <a href="#rfc.xref.draft-ietf-httpbis-content-disp.2">C</a></li>
    20552054               </ul>
    20562055            </li>
     
    22022201                  </li>
    22032202                  <li><em>RFC6151</em>&nbsp;&nbsp;<a href="#RFC6151"><b>10.2</b></a>, <a href="#rfc.xref.RFC6151.1">C</a></li>
     2203                  <li><em>RFC6266</em>&nbsp;&nbsp;<a href="#RFC6266"><b>10.2</b></a>, <a href="#rfc.xref.RFC6266.1">B</a>, <a href="#rfc.xref.RFC6266.2">C</a></li>
    22042204               </ul>
    22052205            </li>
Note: See TracChangeset for help on using the changeset viewer.