Changeset 1140 for draft-ietf-httpbis-content-disp
- Timestamp:
- 25/02/11 09:27:18 (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
r1139 r1140 365 365 } 366 366 @bottom-center { 367 content: "Expires August 2 8, 2011";367 content: "Expires August 29, 2011"; 368 368 } 369 369 @bottom-right { … … 405 405 <meta name="dct.creator" content="Reschke, J. F."> 406 406 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-content-disp-latest"> 407 <meta name="dct.issued" scheme="ISO8601" content="2011-02-2 4">407 <meta name="dct.issued" scheme="ISO8601" content="2011-02-25"> 408 408 <meta name="dct.abstract" content="RFC 2616 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."> 409 409 <meta name="description" content="RFC 2616 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."> … … 423 423 <td class="left">Updates: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved) 424 424 </td> 425 <td class="right">February 2 4, 2011</td>425 <td class="right">February 25, 2011</td> 426 426 </tr> 427 427 <tr> … … 430 430 </tr> 431 431 <tr> 432 <td class="left">Expires: August 2 8, 2011</td>432 <td class="left">Expires: August 29, 2011</td> 433 433 <td class="right"></td> 434 434 </tr> … … 459 459 in progress”. 460 460 </p> 461 <p>This Internet-Draft will expire on August 2 8, 2011.</p>461 <p>This Internet-Draft will expire on August 29, 2011.</p> 462 462 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 463 463 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 674 674 filename*=utf-8''<b>%e2%82%ac</b>%20rates 675 675 </pre> <p>Note: as of February 2011, those user agents that do not support the RFC 5987 encoding ignore "filename*" when it occurs after 676 "filename". Unfortunately, some user agents that do support RFC 5987 do pickthe "filename" rather than the "filename*" parameter676 "filename". Unfortunately, one user agent that does support RFC 5987 picks the "filename" rather than the "filename*" parameter 677 677 when it occurs first; it is expected that this situation is going to improve soon. 678 678 </p> … … 902 902 </table> 903 903 </div> 904 <p id="rfc.section.C.4.p.3">(*) Does not implement the fallback behavior to "filename" described in <a href="#disposition.parameter.filename" title="Disposition Parameter: 'Filename'">Section 4.3</a> .904 <p id="rfc.section.C.4.p.3">(*) Does not implement the fallback behavior to "filename" described in <a href="#disposition.parameter.filename" title="Disposition Parameter: 'Filename'">Section 4.3</a>; a fix is planned for Firefox 5. 905 905 </p> 906 906 <p id="rfc.section.C.4.p.4">(**) Starting with IE9RC, but only implements UTF-8.</p> … … 974 974 <p id="rfc.section.D.10.p.1">Editorial changes: Fixed two typos where the new Conformance section said "Content-Location" instead of "Content-Disposition". 975 975 Cleaned up terminology ("user agent", "recipient", "sender", "message body", ...). Stated what the escape character for quoted-string 976 is. Explained a use case for "inline" disposition type. 976 is. Explained a use case for "inline" disposition type. Updated implementation notes with respect to the fallback behavior. 977 977 </p> 978 978 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> -
draft-ietf-httpbis-content-disp/latest/draft-ietf-httpbis-content-disp.xml
r1139 r1140 355 355 Note: as of February 2011, those user agents that do not support the RFC 5987 356 356 encoding ignore "filename*" when it occurs after "filename". Unfortunately, 357 some user agents that do support RFC 5987 do pickthe "filename" rather357 one user agent that does support RFC 5987 picks the "filename" rather 358 358 than the "filename*" parameter when it occurs first; it is expected that 359 359 this situation is going to improve soon. … … 822 822 <t> 823 823 (*) Does not implement the fallback behavior to "filename" described in 824 <xref target="disposition.parameter.filename"/> .824 <xref target="disposition.parameter.filename"/>; a fix is planned for Firefox 5. 825 825 </t> 826 826 <t> … … 981 981 of "Content-Disposition". Cleaned up terminology ("user agent", "recipient", 982 982 "sender", "message body", ...). Stated what the escape character for quoted-string 983 is. Explained a use case for "inline" disposition type. 983 is. Explained a use case for "inline" disposition type. Updated implementation 984 notes with respect to the fallback behavior. 984 985 </t> 985 986 </section>
Note: See TracChangeset
for help on using the changeset viewer.