Ignore:
Timestamp:
Sep 12, 2010, 11:50:47 AM (9 years ago)
Author:
julian.reschke@…
Message:

some editorial improvements based on Bjoern Hoehrmann's feedback.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis-content-disp/latest/draft-ietf-httpbis-content-disp.html

    r996 r997  
    401401      <meta name="dct.creator" content="Reschke, J. F.">
    402402      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-content-disp-latest">
    403       <meta name="dct.issued" scheme="ISO8601" content="2010-09-10">
     403      <meta name="dct.issued" scheme="ISO8601" content="2010-09-12">
    404404      <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.">
    405405      <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.">
     
    419419               <td class="left">Updates: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved)
    420420               </td>
    421                <td class="right">September 10, 2010</td>
     421               <td class="right">September 12, 2010</td>
    422422            </tr>
    423423            <tr>
     
    426426            </tr>
    427427            <tr>
    428                <td class="left">Expires: March 14, 2011</td>
     428               <td class="left">Expires: March 16, 2011</td>
    429429               <td class="right"></td>
    430430            </tr>
     
    455455         in progress”.
    456456      </p>
    457       <p>This Internet-Draft will expire on March 14, 2011.</p>
     457      <p>This Internet-Draft will expire on March 16, 2011.</p>
    458458      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    459459      <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    574574         being displayed).
    575575      </p>
    576       <p id="rfc.section.3.3.p.3">"filename" and "filename*" behave the same, except 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 support
     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 support
    577577         "filename*".
    578578      </p>
     
    607607      </h1>
    608608      <div id="rfc.figure.u.4"></div>
    609       <p>Direct UA to show "save as" dialog, with a filename of "foo.html":</p>  <pre class="text">Content-Disposition: Attachment; filename=foo.html
     609      <p>Direct UA to show "save as" dialog, with a filename of "example.html":</p>  <pre class="text">Content-Disposition: Attachment; filename=example.html
    610610</pre><div id="rfc.figure.u.5"></div>
    611       <p>Direct UA to behave as if the Content-Disposition header field wasn't present, but to remember the filename "foo.html" for
    612          a subsequent save operation:
    613       </p>  <pre class="text">Content-Disposition: INLINE; FILENAME= "foo.html"
     611      <p>Direct UA to behave as if the Content-Disposition header field wasn't present, but to remember the filename "example.html"
     612         for a subsequent save operation:
     613      </p>  <pre class="text">Content-Disposition: INLINE; FILENAME= "example.html"
    614614</pre><div id="rfc.figure.u.6"></div>
    615615      <p>Direct UA to show "save as" dialog, with a filename of "an example":</p>  <pre class="text">Content-Disposition: Attachment; Filename*=UTF-8'<b>en</b>'an<b>%20</b>example
     
    618618      </p>
    619619      <div id="rfc.figure.u.7"></div>
    620       <p>Direct UA to show "save as" dialog, with a filename containing the Unicode character U+20AC (EURO SIGN):</p>  <pre class="text">Content-Disposition: attachment; filename*= UTF-8''<b>%e2%82%ac</b>%20rates
     620      <p>Direct UA to show "save as" dialog, with a filename containing the Unicode character U+20AC (EURO SIGN):</p>  <pre class="text">Content-Disposition: attachment;
     621                     filename*= UTF-8''<b>%e2%82%ac</b>%20rates
    621622</pre>  <p>Here, the encoding defined in <a href="#RFC5987" id="rfc.xref.RFC5987.5"><cite title="Applicability of RFC 2231 Encoding to Hypertext Transfer Protocol (HTTP) Headers">[RFC5987]</cite></a> is also used to encode the non-ISO-8859-1 character.
    622623      </p>
    623624      <div id="rfc.figure.u.8"></div>
    624       <p>Same as above, but adding the "filename" parameter for compatibility with user agents not implementing RFC 5987:</p>  <pre class="text">Content-Disposition: attachment; filename="EURO rates";
    625                                  filename*=utf-8''<b>%e2%82%ac</b>%20rates
     625      <p>Same as above, but adding the "filename" parameter for compatibility with user agents not implementing RFC 5987:</p>  <pre class="text">Content-Disposition: attachment;
     626                     filename="EURO rates";
     627                     filename*=utf-8''<b>%e2%82%ac</b>%20rates
    626628</pre>  <p>Note: as of September 2010, those user agents that do not support the RFC 5987 encoding ignore "filename*" when it occurs
    627629         after "filename". Unfortunately, some user agents that do support RFC 5987 do pick the "filename" rather than the "filename*"
     
    663665      <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;Acknowledgements
    664666      </h1>
    665       <p id="rfc.section.8.p.1">Thanks to Rolf Eike Beer, Alfred Hoenes, Roar Lauritzsen, and Henrik Nordstrom for their valuable feedback.</p>
     667      <p id="rfc.section.8.p.1">Thanks to Rolf Eike Beer, Bjoern Hoehrmann, Alfred Hoenes, Roar Lauritzsen, and Henrik Nordstrom for their valuable feedback.</p>
    666668      <h1 id="rfc.references"><a id="rfc.section.9" href="#rfc.section.9">9.</a> References
    667669      </h1>
Note: See TracChangeset for help on using the changeset viewer.