Changes between Version 3 and Version 4 of ContentDispositionProducerAdvice


Ignore:
Timestamp:
Jul 13, 2011, 5:36:44 AM (8 years ago)
Author:
mnot@…
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ContentDispositionProducerAdvice

    v3 v4  
    2121}}}
    2222
    23 However, when the filename has non-ASCII characters in it, it needs to be encoded as described in RFC5987. For example:
     23However, when the filename has non-ISO-8859-1 characters in it, it needs to be encoded as described in RFC5987. For example:
    2424
    2525{{{
     
    6363=== Why shouldn't I just produce the C-D header in UTF-8 directly? ===
    6464
     65HTTP headers are defined to be ISO-8859-1, so encoding them as UTF-8 assumes that the client will correctly "sniff" the encoding.
     66
     67Unfortunately, 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.