Changes between Version 3 and Version 4 of ContentDispositionProducerAdvice

Timestamp:

13/07/11 12:36:44 (11 years ago)

Author:

mnot@…

Comment:

--

ContentDispositionProducerAdvice

@@ -21 +21 @@
 }}}
 
-However, when the filename has non-ASCII characters in it, it needs to be encoded as described in RFC5987. For example:
+However, when the filename has non-ISO-8859-1 characters in it, it needs to be encoded as described in RFC5987. For example:
 
 {{{
@@ -63 +63 @@
 === Why shouldn't I just produce the C-D header in UTF-8 directly? ===
 
+HTTP headers are defined to be ISO-8859-1, so encoding them as UTF-8 assumes that the client will correctly "sniff" the encoding.
+
+Unfortunately, there are some UTF-8 characters that look like ISO-8859-1 characters, such as an a with an umlaut (ä). In these cases, some browsers will treat it as UTF-8, even though it's valid ISO-8859-1, causing a loss of interoperability; your users will see the wrong filename. See [http://greenbytes.de/tech/tc2231/#attwithutf8fnplain the test case] for details.