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

Timestamp:

15/09/10 13:34:47 (12 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.xml (modified) (2 diffs)

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

@@ -182 +182 @@
   the encoding defined in <xref target="RFC5987"/>, allowing the use 
   of characters not present in the ISO-8859-1 character set (<xref target="ISO-8859-1"/>).
-  When both "filename" and "filename*" are present, a recipient &SHOULD; pick
-  "filename*" and ignore "filename" - this will make it possible to send the
-  same header field value to clients that do not support "filename*".
+</t>
+<t>
+  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
+  &SHOULD; 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 <xref target="examples"/> for 
+  an example).
 </t>
 <t>
@@ -231 +238 @@
 </section>  
 
-<section title="Examples">
+<section title="Examples" anchor="examples">
 
 <figure>