Changeset 1259
- Timestamp:
- 04/04/11 17:08:48 (11 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p3-payload.html
r1258 r1259 1605 1605 <h2 id="rfc.references.2"><a href="#rfc.section.10.2" id="rfc.section.10.2">10.2</a> Informative References 1606 1606 </h2> 1607 <table> 1607 <table> 1608 1608 <tr> 1609 1609 <td class="reference"><b id="BCP97">[BCP97]</b></td> … … 1679 1679 <td class="reference"><b id="RFC5322">[RFC5322]</b></td> 1680 1680 <td class="top">Resnick, P., “<a href="http://tools.ietf.org/html/rfc5322">Internet Message Format</a>”, RFC 5322, October 2008. 1681 </td> 1682 </tr> 1683 <tr> 1684 <td class="reference"><b id="draft-ietf-httpbis-content-disp">[draft-ietf-httpbis-content-disp]</b></td> 1685 <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. 1681 1686 </td> 1682 1687 </tr> … … 1763 1768 experimental deployment found lacking that are now addressed in the base HTTP/1.1 specification. 1764 1769 </p> 1765 <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="# RFC2076" id="rfc.xref.RFC2076.1"><cite title="Common Internet Message Headers">[RFC2076]</cite></a>).1770 <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>). 1766 1771 </p> 1767 1772 <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> … … 1778 1783 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>) 1779 1784 </p> 1780 <p id="rfc.section.C.p.6">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>) 1785 <p id="rfc.section.C.p.6">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>) 1786 </p> 1787 <p id="rfc.section.C.p.7">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>) 1781 1788 </p> 1782 1789 <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a> <a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1> … … 2084 2091 <li><a id="rfc.index.D" href="#rfc.index.D"><b>D</b></a><ul> 2085 2092 <li>deflate (Coding Format) <a href="#rfc.iref.d.1">2.2</a></li> 2093 <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> 2086 2094 </ul> 2087 2095 </li> -
draft-ietf-httpbis/latest/p3-payload.xml
r1254 r1259 2392 2392 </reference> 2393 2393 2394 <reference anchor="draft-ietf-httpbis-content-disp"> 2395 <front> 2396 <title abbrev="Content-Disposition in HTTP">Use of the Content-Disposition Header Field 2397 in the Hypertext Transfer Protocol (HTTP)</title> 2398 <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke"> 2399 <organization abbrev="greenbytes">greenbytes GmbH</organization> 2400 <address> 2401 <email>julian.reschke@greenbytes.de</email> 2402 </address> 2403 </author> 2404 <date month="March" year="2011" day="28"/> 2405 </front> 2406 <seriesInfo name='Internet-Draft' value='draft-ietf-httpbis-content-disp-09' /> 2407 </reference> 2394 2408 2395 2409 </references> … … 2548 2562 <t> 2549 2563 A number of other header fields, such as Content-Disposition and Title, 2550 from SMTP and MIME are also often implemented (see <xref target="RFC2076"/>). 2564 from SMTP and MIME are also often implemented (see <xref target="draft-ietf-httpbis-content-disp"/> 2565 and <xref target="RFC2076"/>). 2551 2566 </t> 2552 2567 </section> … … 2576 2591 of potentially breaking relative links in content-negotiated resources. 2577 2592 (<xref target="header.content-location"/>) 2593 </t> 2594 <t> 2595 Remove discussion of Content-Disposition header field, it is now defined 2596 by <xref target="draft-ietf-httpbis-content-disp"/>. 2597 (<xref target="additional.features"/>) 2578 2598 </t> 2579 2599 <t>
Note: See TracChangeset
for help on using the changeset viewer.