Changeset 1008 for draft-ietf-httpbis-content-disp
- Timestamp:
- 15/09/10 12:48:21 (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
r1005 r1008 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-1 4">403 <meta name="dct.issued" scheme="ISO8601" content="2010-09-15"> 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 1 4, 2010</td>421 <td class="right">September 15, 2010</td> 422 422 </tr> 423 423 <tr> … … 426 426 </tr> 427 427 <tr> 428 <td class="left">Expires: March 1 8, 2011</td>428 <td class="left">Expires: March 19, 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 8, 2011.</p>457 <p>This Internet-Draft will expire on March 19, 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> … … 574 574 being displayed). 575 575 </p> 576 <p id="rfc.section.3.3.p.3">The parameters "filename" and "filename*" differ only in that "filename*" uses the encoding defined in <a href="#RFC5987" id="rfc.xref.RFC5987.3"><cite title="Applicability of RFC 2231 Encoding to Hypertext Transfer Protocol (HTTP) Headers">[RFC5987]</cite></a>, allowing the use of characters not present in the ISO-8859-1 character set (<a href="#ISO-8859-1" id="rfc.xref.ISO-8859-1.1"><cite title="Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1">[ISO-8859-1]</cite></a>). When both "filename" and "filename*" are present, a recipient <em class="bcp14">SHOULD</em> pick "filename*" and ignore "filename" - this will make it possible to send the same header value to clients that do not support577 "filename*".576 <p id="rfc.section.3.3.p.3">The parameters "filename" and "filename*" differ only in that "filename*" uses the encoding defined in <a href="#RFC5987" id="rfc.xref.RFC5987.3"><cite title="Applicability of RFC 2231 Encoding to Hypertext Transfer Protocol (HTTP) Headers">[RFC5987]</cite></a>, allowing the use of characters not present in the ISO-8859-1 character set (<a href="#ISO-8859-1" id="rfc.xref.ISO-8859-1.1"><cite title="Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1">[ISO-8859-1]</cite></a>). When both "filename" and "filename*" are present, a recipient <em class="bcp14">SHOULD</em> pick "filename*" and ignore "filename" - this will make it possible to send the same header field value to clients that do 577 not support "filename*". 578 578 </p> 579 579 <p id="rfc.section.3.3.p.4">It is essential that user agents treat the specified filename as advisory only, thus be very careful in extracting the desired -
draft-ietf-httpbis-content-disp/latest/draft-ietf-httpbis-content-disp.xml
r1005 r1008 184 184 When both "filename" and "filename*" are present, a recipient &SHOULD; pick 185 185 "filename*" and ignore "filename" - this will make it possible to send the 186 same header value to clients that do not support "filename*".186 same header field value to clients that do not support "filename*". 187 187 </t> 188 188 <t>
Note: See TracChangeset
for help on using the changeset viewer.