Comment 4 for bug 483174

Ok so, the bug is fixed. We now use both encoding: RFC2231 and plain URLEncoded.

However there is still no standard way to put a chinese name in a Content-Disposition header that will work on any browser. Check here: http://greenbytes.de/tech/tc2231/

It will work on firefox (as it support RFC2231) perhaps on some IE using the URLEncoded bug, but not on Safari nor Chrome.

The only way to have a proper name is to use the name in the URL: /files/测试图片.gif and let the browser safe the file using the URL name.