Changeset 995 for draft-ietf-httpbis-content-disp
- Timestamp:
- 09/09/10 13:09:34 (12 years ago)
- Location:
- draft-ietf-httpbis-content-disp/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis-content-disp/latest/draft-ietf-httpbis-content-disp.html
r993 r995 401 401 <meta name="dct.creator" content="Reschke, J. F."> 402 402 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-content-disp-latest"> 403 <meta name="dct.issued" scheme="ISO8601" content="2010-09-0 7">403 <meta name="dct.issued" scheme="ISO8601" content="2010-09-09"> 404 404 <meta name="dct.abstract" content="HTTP/1.1 defines the Content-Disposition response header field, but points out that it is not part of the HTTP/1.1 Standard. This specification takes over the definition and registration of Content-Disposition, as used in HTTP, and clarifies internationalization aspects."> 405 405 <meta name="description" content="HTTP/1.1 defines the Content-Disposition response header field, but points out that it is not part of the HTTP/1.1 Standard. This specification takes over the definition and registration of Content-Disposition, as used in HTTP, and clarifies internationalization aspects."> … … 419 419 <td class="left">Updates: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved) 420 420 </td> 421 <td class="right">September 7, 2010</td>421 <td class="right">September 9, 2010</td> 422 422 </tr> 423 423 <tr> … … 426 426 </tr> 427 427 <tr> 428 <td class="left">Expires: March 1 1, 2011</td>428 <td class="left">Expires: March 13, 2011</td> 429 429 <td class="right"></td> 430 430 </tr> … … 455 455 in progress”. 456 456 </p> 457 <p>This Internet-Draft will expire on March 1 1, 2011.</p>457 <p>This Internet-Draft will expire on March 13, 2011.</p> 458 458 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 459 459 <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 635 635 <p id="rfc.section.6.p.1">Using server-supplied information for constructing local filenames introduces many risks. These are summarized in <a href="#disposition.parameter.filename" title="Disposition Parameter: 'Filename'">Section 3.3</a>. 636 636 </p> 637 <p id="rfc.section.6.p.2">Furthermore, implementers also ought to be aware of the Security Considerations applying to HTTP (see <a href="http://tools.ietf.org/html/rfc2616#section-15">Section 15</a> of <a href="#RFC2616" id="rfc.xref.RFC2616.7"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>), and also the parameter encoding defined in <a href="#RFC5987" id="rfc.xref.RFC5987.7"><cite title="Applicability of RFC 2231 Encoding to Hypertext Transfer Protocol (HTTP) Headers">[RFC5987]</cite></a> (see <a href=" #RFC5987" id="rfc.xref.RFC5987.8"><cite title="Applicability of RFC 2231 Encoding to Hypertext Transfer Protocol (HTTP) Headers">[RFC5987]</cite></a>).637 <p id="rfc.section.6.p.2">Furthermore, implementers also ought to be aware of the Security Considerations applying to HTTP (see <a href="http://tools.ietf.org/html/rfc2616#section-15">Section 15</a> of <a href="#RFC2616" id="rfc.xref.RFC2616.7"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>), and also the parameter encoding defined in <a href="#RFC5987" id="rfc.xref.RFC5987.7"><cite title="Applicability of RFC 2231 Encoding to Hypertext Transfer Protocol (HTTP) Headers">[RFC5987]</cite></a> (see <a href="http://tools.ietf.org/html/rfc5987#section-5" id="rfc.xref.RFC5987.8">Section 5</a>). 638 638 </p> 639 639 <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a> <a id="iana.considerations" href="#iana.considerations">IANA Considerations</a></h1> … … 929 929 <li class="indline1"><em>RFC5987</em> <a class="iref" href="#rfc.xref.RFC5987.1">3.1</a>, <a class="iref" href="#rfc.xref.RFC5987.2">3.1</a>, <a class="iref" href="#rfc.xref.RFC5987.3">3.3</a>, <a class="iref" href="#rfc.xref.RFC5987.4">4</a>, <a class="iref" href="#rfc.xref.RFC5987.5">4</a>, <a class="iref" href="#rfc.xref.RFC5987.6">5</a>, <a class="iref" href="#rfc.xref.RFC5987.7">6</a>, <a class="iref" href="#rfc.xref.RFC5987.8">6</a>, <a class="iref" href="#RFC5987"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.RFC5987.9">A</a>, <a class="iref" href="#rfc.xref.RFC5987.10">C</a><ul class="ind"> 930 930 <li class="indline1"><em>Section 3.2</em> <a class="iref" href="#rfc.xref.RFC5987.2">3.1</a></li> 931 <li class="indline1"><em>Section 5</em> <a class="iref" href="#rfc.xref.RFC5987.8">6</a></li> 931 932 </ul> 932 933 </li> -
draft-ietf-httpbis-content-disp/latest/draft-ietf-httpbis-content-disp.xml
r993 r995 316 316 Furthermore, implementers also ought to be aware of the Security 317 317 Considerations applying to HTTP (see <xref target="RFC2616" x:fmt="of" x:sec="15"/>), and also the parameter encoding defined in <xref target="RFC5987"/> 318 (see <xref target="RFC5987" x:fmt="sec" x: rel="#security.considerations"/>).318 (see <xref target="RFC5987" x:fmt="sec" x:sec="5"/>). 319 319 </t> 320 320 </section>
Note: See TracChangeset
for help on using the changeset viewer.