* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Changeset 1074


Ignore:
Timestamp:
2010-11-03 04:10:20 (4 years ago)
Author:
julian.reschke@gmx.de
Message:

note that the language tagging on filenames is likely to be ignored by recipients (see #264)

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

    r1073 r1074  
    404404      <meta name="dct.creator" content="Reschke, J. F."> 
    405405      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-content-disp-latest"> 
    406       <meta name="dct.issued" scheme="ISO8601" content="2010-11-02"> 
     406      <meta name="dct.issued" scheme="ISO8601" content="2010-11-03"> 
    407407      <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."> 
    408408      <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."> 
     
    422422               <td class="left">Updates: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved) 
    423423               </td> 
    424                <td class="right">November 2, 2010</td> 
     424               <td class="right">November 3, 2010</td> 
    425425            </tr> 
    426426            <tr> 
     
    429429            </tr> 
    430430            <tr> 
    431                <td class="left">Expires: May 6, 2011</td> 
     431               <td class="left">Expires: May 7, 2011</td> 
    432432               <td class="right"></td> 
    433433            </tr> 
     
    458458         in progress”. 
    459459      </p> 
    460       <p>This Internet-Draft will expire on May 6, 2011.</p> 
     460      <p>This Internet-Draft will expire on May 7, 2011.</p> 
    461461      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 
    462462      <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> 
     
    572572      <p id="rfc.section.3.1.p.5">Note that due to the rules for implied linear whitespace (<a href="http://tools.ietf.org/html/rfc2616#section-2.1">Section 2.1</a> of <a href="#RFC2616" id="rfc.xref.RFC2616.8"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>), OPTIONAL whitespace can appear between words (token or quoted-string) and separator characters. 
    573573      </p> 
     574      <p id="rfc.section.3.1.p.6">Furthermore note that the format used for ext-value allows specifying a natural language; this is of limited use for filenames 
     575         and is likely to be ignored by recipients. 
     576      </p> 
    574577      <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a id="disposition.type" href="#disposition.type">Disposition Type</a></h2> 
    575578      <p id="rfc.section.3.2.p.1">If the disposition type matches "attachment" (case-insensitively), this indicates that the user agent should prompt the user 
     
    634637      <p>Direct UA to show "save as" dialog, with a filename of "example.html":</p>  <pre class="text">Content-Disposition: Attachment; filename=example.html 
    635638</pre><div id="rfc.figure.u.5"></div>  
    636       <p>Direct UA to behave as if the Content-Disposition header field wasn't present, but to remember the filename "example.html" 
     639      <p>Direct UA to behave as if the Content-Disposition header field wasn't present, but to remember the filename "an example.html" 
    637640         for a subsequent save operation: 
    638       </p>  <pre class="text">Content-Disposition: INLINE; FILENAME= "example.html" 
    639 </pre><div id="rfc.figure.u.6"></div>  
    640       <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 
    641 </pre>  <p>Note that this example uses the extended encoding defined in <a href="#RFC5987" id="rfc.xref.RFC5987.4"><cite title="Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters">[RFC5987]</cite></a> to specify that the natural language of the filename is English, and also to encode the space character which is not allowed 
    642          in the token production. 
     641      </p>  <pre class="text">Content-Disposition: INLINE; FILENAME= "an example.html" 
     642</pre>  <p>Note: this uses the quoted-string form so that the space character can be included.</p>  
     643      <div id="rfc.figure.u.6"></div>  
     644      <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;  
     645                     filename*= UTF-8''<b>%e2%82%ac</b>%20rates 
     646</pre>  <p>Here, the encoding defined in <a href="#RFC5987" id="rfc.xref.RFC5987.4"><cite title="Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters">[RFC5987]</cite></a> is also used to encode the non-ISO-8859-1 character. 
    643647      </p>  
    644648      <div id="rfc.figure.u.7"></div>  
    645       <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;  
    646                      filename*= UTF-8''<b>%e2%82%ac</b>%20rates 
    647 </pre>  <p>Here, the encoding defined in <a href="#RFC5987" id="rfc.xref.RFC5987.5"><cite title="Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters">[RFC5987]</cite></a> is also used to encode the non-ISO-8859-1 character. 
    648       </p>  
    649       <div id="rfc.figure.u.8"></div>  
    650649      <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; 
    651650                     filename="EURO rates"; 
     
    656655      </p>  
    657656      <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a id="i18n" href="#i18n">Internationalization Considerations</a></h1> 
    658       <p id="rfc.section.5.p.1">The "filename*" parameter (<a href="#disposition.parameter.filename" title="Disposition Parameter: 'Filename'">Section&nbsp;3.3</a>), using the encoding defined in <a href="#RFC5987" id="rfc.xref.RFC5987.6"><cite title="Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters">[RFC5987]</cite></a>, allows the server to transmit characters outside the ISO-8859-1 character set, and also to optionally specify the language 
     657      <p id="rfc.section.5.p.1">The "filename*" parameter (<a href="#disposition.parameter.filename" title="Disposition Parameter: 'Filename'">Section&nbsp;3.3</a>), using the encoding defined in <a href="#RFC5987" id="rfc.xref.RFC5987.5"><cite title="Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters">[RFC5987]</cite></a>, allows the server to transmit characters outside the ISO-8859-1 character set, and also to optionally specify the language 
    659658         in use. 
    660659      </p> 
     
    663662      <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&nbsp;3.3</a>. 
    664663      </p> 
    665       <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.9"><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="Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters">[RFC5987]</cite></a> (see <a href="http://tools.ietf.org/html/rfc5987#section-5" id="rfc.xref.RFC5987.8">Section 5</a>). 
     664      <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.9"><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.6"><cite title="Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters">[RFC5987]</cite></a> (see <a href="http://tools.ietf.org/html/rfc5987#section-5" id="rfc.xref.RFC5987.7">Section 5</a>). 
    666665      </p> 
    667666      <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="iana.considerations" href="#iana.considerations">IANA Considerations</a></h1> 
     
    774773         <li>The definition for the disposition type "inline" (<a href="#RFC2183" id="rfc.xref.RFC2183.6"><cite title="Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field">[RFC2183]</cite></a>, <a href="http://tools.ietf.org/html/rfc2183#section-2.1">Section 2.1</a>) has been re-added with a suggestion for its processing. 
    775774         </li> 
    776          <li>This specification requires support for the extended parameter encoding defined in <a href="#RFC5987" id="rfc.xref.RFC5987.9"><cite title="Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters">[RFC5987]</cite></a>. 
     775         <li>This specification requires support for the extended parameter encoding defined in <a href="#RFC5987" id="rfc.xref.RFC5987.8"><cite title="Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters">[RFC5987]</cite></a>. 
    777776         </li> 
    778777      </ul> 
     
    785784      </p> 
    786785      <p id="rfc.section.C.p.2">Unfortunately, user agent implementers have not managed to come up with an interoperable approach, although the IETF Standards 
    787          Track specifies exactly one solution (<a href="#RFC2231" id="rfc.xref.RFC2231.1"><cite title="MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations">[RFC2231]</cite></a>, clarified and profiled for HTTP in <a href="#RFC5987" id="rfc.xref.RFC5987.10"><cite title="Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters">[RFC5987]</cite></a>). 
     786         Track specifies exactly one solution (<a href="#RFC2231" id="rfc.xref.RFC2231.1"><cite title="MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations">[RFC2231]</cite></a>, clarified and profiled for HTTP in <a href="#RFC5987" id="rfc.xref.RFC5987.9"><cite title="Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters">[RFC5987]</cite></a>). 
    788787      </p> 
    789788      <p id="rfc.section.C.p.3">For completeness, the sections below describe the various approaches that have been tried, and explains how they are inferior 
     
    930929         </li> 
    931930         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/258">http://tools.ietf.org/wg/httpbis/trac/ticket/258</a>&gt;: "Avoid passive voice in message requirements" 
     931         </li> 
     932         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/264">http://tools.ietf.org/wg/httpbis/trac/ticket/264</a>&gt;: "add explanation of language tagging" 
    932933         </li> 
    933934      </ul> 
     
    983984                     </ul> 
    984985                  </li> 
    985                   <li><em>RFC5987</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5987.1">3.1</a>, <a href="#rfc.xref.RFC5987.2">3.1</a>, <a href="#rfc.xref.RFC5987.3">3.3</a>, <a href="#rfc.xref.RFC5987.4">4</a>, <a href="#rfc.xref.RFC5987.5">4</a>, <a href="#rfc.xref.RFC5987.6">5</a>, <a href="#rfc.xref.RFC5987.7">6</a>, <a href="#rfc.xref.RFC5987.8">6</a>, <a href="#RFC5987"><b>9.1</b></a>, <a href="#rfc.xref.RFC5987.9">A</a>, <a href="#rfc.xref.RFC5987.10">C</a><ul> 
     986                  <li><em>RFC5987</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5987.1">3.1</a>, <a href="#rfc.xref.RFC5987.2">3.1</a>, <a href="#rfc.xref.RFC5987.3">3.3</a>, <a href="#rfc.xref.RFC5987.4">4</a>, <a href="#rfc.xref.RFC5987.5">5</a>, <a href="#rfc.xref.RFC5987.6">6</a>, <a href="#rfc.xref.RFC5987.7">6</a>, <a href="#RFC5987"><b>9.1</b></a>, <a href="#rfc.xref.RFC5987.8">A</a>, <a href="#rfc.xref.RFC5987.9">C</a><ul> 
    986987                        <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5987.2">3.1</a></li> 
    987                         <li><em>Section 5</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5987.8">6</a></li> 
     988                        <li><em>Section 5</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5987.7">6</a></li> 
    988989                     </ul> 
    989990                  </li> 
  • draft-ietf-httpbis-content-disp/latest/draft-ietf-httpbis-content-disp.xml

    r1073 r1074  
    165165  appear between words (token or quoted-string) and separator characters. 
    166166</t> 
    167  
     167<t> 
     168  Furthermore note that the format used for ext-value allows specifying a 
     169  natural language; this is of limited use for filenames and is likely to be 
     170  ignored by recipients. 
     171</t> 
    168172</section> 
    169173 
     
    282286<preamble> 
    283287Direct UA to behave as if the Content-Disposition header field wasn't present, 
    284 but to remember the filename "example.html" for a subsequent save operation: 
     288but to remember the filename "an example.html" for a subsequent save operation: 
    285289</preamble> 
    286290<artwork type="example" x:indent-with="  "> 
    287 Content-Disposition: INLINE; FILENAME= "example.html" 
    288 </artwork></figure> 
    289 <figure> 
    290 <preamble> 
    291 Direct UA to show "save as" dialog, with a filename of "an example": 
    292 </preamble> 
    293 <artwork type="example"> 
    294 Content-Disposition: Attachment; Filename*=UTF-8'<x:highlight>en</x:highlight>'an<x:highlight>%20</x:highlight>example 
     291Content-Disposition: INLINE; FILENAME= "an example.html" 
    295292</artwork> 
    296 <postamble>Note that this example uses the extended encoding defined in 
    297 <xref target="RFC5987"/> to specify that the natural language of the filename 
    298 is English, and also to encode the space character which is not allowed in the 
    299 token production. 
     293<postamble> 
     294  Note: this uses the quoted-string form so that the space character 
     295  can be included. 
    300296</postamble> 
    301297</figure> 
     
    889885      "Avoid passive voice in message requirements" 
    890886    </t> 
     887    <t> 
     888      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/264"/>: 
     889      "add explanation of language tagging" 
     890    </t> 
    891891  </list> 
    892892</t> 
Note: See TracChangeset for help on using the changeset viewer.