Changeset 1011 for draft-ietf-httpbis-content-disp/latest/draft-ietf-httpbis-content-disp.html

Timestamp:

Sep 15, 2010, 6:34:47 AM (9 years ago)

Author:

julian.reschke@…

Message:

rephrase the paragraph defining the filename/filename* fallback behavior

File:

• draft-ietf-httpbis-content-disp/latest/draft-ietf-httpbis-content-disp.html (modified) (3 diffs)

draft-ietf-httpbis-content-disp/latest/draft-ietf-httpbis-content-disp.html

@@ -476 +476 @@
             </ul>
          </li>
-         <li class="tocline0">4.&nbsp;&nbsp;&nbsp;<a href="#rfc.section.4">Examples</a></li>
+         <li class="tocline0">4.&nbsp;&nbsp;&nbsp;<a href="#examples">Examples</a></li>
          <li class="tocline0">5.&nbsp;&nbsp;&nbsp;<a href="#i18n">Internationalization Considerations</a></li>
          <li class="tocline0">6.&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a></li>
@@ -574 +574 @@
          being displayed).
       </p>
-      <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="Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters">[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
-         not support "filename*".
-      </p>
-      <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
+      <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="Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters">[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>).
+      </p>
+      <p id="rfc.section.3.3.p.4">Many user agent implementations predating this specification do not understand the "filename*" parameter. Therefore, when
+         both "filename" and "filename*" are present in a single header field value, recipients <em class="bcp14">SHOULD</em> pick "filename*" and ignore "filename". This way, senders can avoid special-casing specific user agents by sending both the
+         more expressive "filename*" parameter, and the "filename" parameter as fallback for legacy recipients (see <a href="#examples" title="Examples">Section&nbsp;4</a> for an example).
+      </p>
+      <p id="rfc.section.3.3.p.5">It is essential that user agents treat the specified filename as advisory only, thus be very careful in extracting the desired
          information. In particular: 
       </p>
@@ -604 +607 @@
          using Content-Disposition, such as MIME and HTTP. Therefore, not all registered values may make sense in the context of HTTP.
       </p>
-      <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;Examples
-      </h1>
+      <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a id="examples" href="#examples">Examples</a></h1>
       <div id="rfc.figure.u.4"></div> 
       <p>Direct UA to show "save as" dialog, with a filename of "example.html":</p>  <pre class="text">Content-Disposition: Attachment; filename=example.html