Changeset 1307
- Timestamp:
- 10/06/11 07:24:02 (11 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p3-payload.html
r1303 r1307 359 359 } 360 360 @bottom-center { 361 content: "Expires December 3, 2011";361 content: "Expires December 12, 2011"; 362 362 } 363 363 @bottom-right { … … 408 408 <meta name="dct.creator" content="Reschke, J. F."> 409 409 <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"> 411 411 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 412 412 <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 "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 3 defines HTTP message content, metadata, and content negotiation."> … … 434 434 </tr> 435 435 <tr> 436 <td class="left">Expires: December 3, 2011</td>436 <td class="left">Expires: December 12, 2011</td> 437 437 <td class="right">J. Mogul</td> 438 438 </tr> … … 491 491 <tr> 492 492 <td class="left"></td> 493 <td class="right">June 1 , 2011</td>493 <td class="right">June 10, 2011</td> 494 494 </tr> 495 495 </tbody> … … 519 519 in progress”. 520 520 </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> 522 522 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 523 523 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1639 1639 </tr> 1640 1640 <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 draft-ietf-httpbis-content-disp-09 (work in progress), March 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 6266, June 2011. 1643 1643 </td> 1644 1644 </tr> … … 1725 1725 experimental deployment found lacking that are now addressed in the base HTTP/1.1 specification. 1726 1726 </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>). 1728 1728 </p> 1729 1729 <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a> <a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h1> … … 1743 1743 relative links in content-negotiated resources. (<a href="#header.content-location" id="rfc.xref.header.content-location.3" title="Content-Location">Section 6.7</a>) 1744 1744 </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 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 B</a>) 1746 1746 </p> 1747 1747 <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 A.5</a>) … … 2052 2052 <li><a id="rfc.index.D" href="#rfc.index.D"><b>D</b></a><ul> 2053 2053 <li>deflate (Coding Format) <a href="#rfc.iref.d.1">2.2</a></li> 2054 <li><em>draft-ietf-httpbis-content-disp</em> <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>2055 2054 </ul> 2056 2055 </li> … … 2202 2201 </li> 2203 2202 <li><em>RFC6151</em> <a href="#RFC6151"><b>10.2</b></a>, <a href="#rfc.xref.RFC6151.1">C</a></li> 2203 <li><em>RFC6266</em> <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> 2204 2204 </ul> 2205 2205 </li> -
draft-ietf-httpbis/latest/p3-payload.xml
r1303 r1307 2310 2310 </reference> 2311 2311 2312 <reference anchor=" draft-ietf-httpbis-content-disp">2312 <reference anchor="RFC6266"> 2313 2313 <front> 2314 2314 <title abbrev="Content-Disposition in HTTP">Use of the Content-Disposition Header Field … … 2320 2320 </address> 2321 2321 </author> 2322 <date month=" March" year="2011" day="28"/>2322 <date month="June" year="2011"/> 2323 2323 </front> 2324 <seriesInfo name=' Internet-Draft' value='draft-ietf-httpbis-content-disp-09' />2324 <seriesInfo name='RFC' value='6266' /> 2325 2325 </reference> 2326 2326 … … 2480 2480 <t> 2481 2481 A number of other header fields, such as Content-Disposition and Title, 2482 from SMTP and MIME are also often implemented (see <xref target=" draft-ietf-httpbis-content-disp"/>2483 2482 from SMTP and MIME are also often implemented (see <xref target="RFC6266"/> 2483 and <xref target="RFC2076"/>). 2484 2484 </t> 2485 2485 </section> … … 2518 2518 <t> 2519 2519 Remove discussion of Content-Disposition header field, it is now defined 2520 by <xref target=" draft-ietf-httpbis-content-disp"/>.2520 by <xref target="RFC6266"/>. 2521 2521 (<xref target="additional.features"/>) 2522 2522 </t>
Note: See TracChangeset
for help on using the changeset viewer.