blocks|key|1134891|text|我通常对文件名进行URL编码(使用%25xx)，它似乎在所有浏览器中都能工作。不管怎样，你可能想做些测试。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1134892|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I normally URL-encode (with %xx) the filenames, and it seems to work in all browsers. You might want to do some tests anyway.

blocks|key|834341|text|在建议的RFC+5987中讨论了这一点，包括浏览器测试和向后兼容性的链接，“超文本传输协议(HTTP)头字段参数的字符集和语言编码”。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|834342|RFC+2183表示，这样的报头应该按照RFC+2184编码，RFC+2184已经被RFC+2231淘汰，由上面的草案RFC覆盖。|834343|entityMap|0|LINK|mutability|MUTABLE|url|https://www.rfc-editor.org/rfc/rfc5987|1|https://www.rfc-editor.org/rfc/rfc2183|2|https://www.rfc-editor.org/rfc/rfc2184|3|4|https://www.rfc-editor.org/rfc/rfc2231^0|4|8|0|0|0|8|1|K|8|2|V|8|3|16|8|4|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@$A|V|B|W|1|X]]|C|$]]|$1|D|3|E|5|6|7|Y|8|@]|9|@$A|Z|B|10|1|11]|$A|12|B|13|1|14]|$A|15|B|16|1|17]|$A|18|B|19|1|1A]]|C|$]]|$1|F|3|-4|5|6|7|1B|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]|P|$5|I|J|K|C|$L|Q]]|R|$5|I|J|K|C|$L|Q]]|S|$5|I|J|K|C|$L|T]]]]

There is discussion of this, including links to browser testing and backwards compatibility, in the proposed <a href="https://www.rfc-editor.org/rfc/rfc5987" rel="nofollow noreferrer">RFC 5987</a>, &quot;Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters.&quot;
<a href="https://www.rfc-editor.org/rfc/rfc2183" rel="nofollow noreferrer">RFC 2183</a> indicates that such headers should be encoded according to <a href="https://www.rfc-editor.org/rfc/rfc2184" rel="nofollow noreferrer">RFC 2184</a>, which was obsoleted by <a href="https://www.rfc-editor.org/rfc/rfc2231" rel="nofollow noreferrer">RFC 2231</a>, covered by the draft RFC above.

blocks|key|834403|text|以下与RFC草案链接的吉姆在其答复中提到的文档进一步解决了这个问题，在这里肯定值得直接注意：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|834404|HTTP内容配置标头和RFC+2231/2047编码的测试用例|834405|entityMap|0|LINK|mutability|MUTABLE|url|http://greenbytes.de/tech/webdav/draft-reschke-rfc2231-in-http-latest.html|1|https://stackoverflow.com/users/8427/jim|2|http://greenbytes.de/tech/tc2231/^0|3|5|0|B|2|1|0|0|V|2|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]|$A|V|B|W|1|X]]|C|$]]|$1|D|3|E|5|6|7|Y|8|@]|9|@$A|Z|B|10|1|11]]|C|$]]|$1|F|3|-4|5|6|7|12|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]|P|$5|I|J|K|C|$L|Q]]]]

The following document linked from <a href="http://greenbytes.de/tech/webdav/draft-reschke-rfc2231-in-http-latest.html" rel="nofollow noreferrer">the draft RFC</a> mentioned by <a href="https://stackoverflow.com/users/8427/jim">Jim</a> in his answer further addresses the question and definitely worth a direct note here:

<a href="http://greenbytes.de/tech/tc2231/" rel="nofollow noreferrer">Test Cases for HTTP Content-Disposition header and RFC 2231/2047 Encoding</a>

blocks|key|136162|text|在Content-Disposition中没有可互操作的编码非ASCII名称的方法。浏览器兼容性很混乱。|type|unordered-list-item|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|136163|在Content-Disposition中使用UTF-8的Content-Disposition非常奇怪：filename*=UTF-8''foo%25c3%25a4+(是的，这是一个星号，除了中间的空单引号外，没有引号)。|136164|这个标题有点不标准(HTTP/1.1规范承认它的存在，但不要求客户端支持它)。|136165|有一个简单而健壮的替代方案：使用包含您想要的文件名的URL。|unstyled|BOLD|136166|当最后一个斜杠后面的名字是你想要的，你不需要任何额外的标题！|136167|这个技巧奏效了：|136168|/real_script.php/fake_filename.doc|code-block|syntax|javascript|136169|如果您的服务器支持URL重写(例如，Apache中的mod_rewrite+)，那么您可以完全隐藏脚本部分。|136170|URL中的字符应该在UTF-8中，逐个字节地编码：|136171|/mot%25C3%25B6rhead+++#+motörhead|136172|entityMap|0|LINK|mutability|MUTABLE|url|http://greenbytes.de/tech/tc2231/|1|http://www.w3.org/Protocols/rfc2616/rfc2616-sec19.html#sec19.5.1^0|1|J|16|9|0|0|1|J|T|J|1H|Q|0|A|G|1|0|E|8|0|0|0|0|Q|B|0|0|0^^$0|@$1|2|3|4|5|6|7|1C|8|@$9|1D|A|1E|B|C]]|D|@$9|1F|A|1G|1|1H]]|E|$]]|$1|F|3|G|5|6|7|1I|8|@$9|1J|A|1K|B|C]|$9|1L|A|1M|B|C]|$9|1N|A|1O|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|1P|8|@]|D|@$9|1Q|A|1R|1|1S]]|E|$]]|$1|J|3|K|5|L|7|1T|8|@$9|1U|A|1V|B|M]]|D|@]|E|$]]|$1|N|3|O|5|L|7|1W|8|@]|D|@]|E|$]]|$1|P|3|Q|5|L|7|1X|8|@]|D|@]|E|$]]|$1|R|3|S|5|T|7|1Y|8|@]|D|@]|E|$U|V]]|$1|W|3|X|5|L|7|1Z|8|@$9|20|A|21|B|C]]|D|@]|E|$]]|$1|Y|3|Z|5|L|7|22|8|@]|D|@]|E|$]]|$1|10|3|11|5|T|7|23|8|@]|D|@]|E|$U|V]]|$1|12|3|-4|5|L|7|24|8|@]|D|@]|E|$]]]|13|$14|$5|15|16|17|E|$18|19]]|1A|$5|15|16|17|E|$18|1B]]]]

<ul>
<li>There is no interoperable way to encode non-ASCII names in <code>Content-Disposition</code>. <a href="http://greenbytes.de/tech/tc2231/" rel="noreferrer">Browser compatibility is a mess</a>.</li>
<li>The <a href="http://greenbytes.de/tech/webdav/rfc5987.html" rel="noreferrer">theoretically correct syntax</a> for use of UTF-8 in <code>Content-Disposition</code> is very weird: <code>filename*=UTF-8''foo%c3%a4</code> (yes, that's an asterisk, and no quotes except an empty single quote in the middle)</li>
<li>This header is kinda-not-quite-standard (<a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec19.html#sec19.5.1" rel="noreferrer">HTTP/1.1 spec acknowledges its existence</a>, but doesn't require clients to support it).</li>
</ul>

There is a simple and very robust alternative: use a URL that contains the filename you want.

When the name after the last slash is the one you want, you don't need any extra headers!

This trick works:

<pre><code>/real_script.php/fake_filename.doc
</code></pre>

And if your server supports URL rewriting (e.g. <code>mod_rewrite</code> in Apache) then you can fully hide the script part.

Characters in URLs should be in UTF-8, urlencoded byte-by-byte:

<pre><code>/mot%C3%B6rhead # motörhead
</code></pre>

blocks|key|1135140|text|在asp.net+mvc2中，我使用了如下内容：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1135141|return+File(
++++tempFile
++++,+"application/octet-stream"
++++,+HttpUtility.UrlPathEncode(fileName)
++++);|code-block|syntax|javascript|1135142|我想如果您不使用mvc(2)，只需使用|1135143|HttpUtility.UrlPathEncode(fileName)|1135144|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

in asp.net mvc2 i use something like this:

<pre><code>return File(
 tempFile
 , "application/octet-stream"
 , HttpUtility.UrlPathEncode(fileName)
 );
</code></pre>

I guess if you don't use mvc(2) you could just encode the filename using

<pre><code>HttpUtility.UrlPathEncode(fileName)
</code></pre>

blocks|key|834469|text|我知道这是一个旧的职位，但它仍然非常相关。我发现现代浏览器支持rfc5987，它允许utf-8编码，百分比编码(url编码)。然后Na+ve+file.txt变成：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|834470|Content-Disposition:+attachment;+filename*=UTF-8''Na%25C3%25AFve%2520file.txt|code-block|syntax|javascript|834471|Safari+(5)不支持这一点。相反，您应该使用Safari标准将文件名直接写入utf-8编码的标题中：|834472|Content-Disposition:+attachment;+filename=Naïve+file.txt|834473|IE8和更早版本也不支持它，您需要使用utf-8编码的IE标准，百分比编码：|834474|Content-Disposition:+attachment;+filename=Na%25C3%25AFve%2520file.txt|834475|在ASP.Net中，我使用以下代码：|834476|string+contentDisposition;
if+(Request.Browser.Browser+==+"IE"+&&+(Request.Browser.Version+==+"7.0"+%7C%7C+Request.Browser.Version+==+"8.0"))
++++contentDisposition+=+"attachment;+filename="+%2B+Uri.EscapeDataString(fileName);
else+if+(Request.Browser.Browser+==+"Safari")
++++contentDisposition+=+"attachment;+filename="+%2B+fileName;
else
++++contentDisposition+=+"attachment;+filename*=UTF-8''"+%2B+Uri.EscapeDataString(fileName);
Response.AddHeader("Content-Disposition",+contentDisposition);|834477|我用IE7，IE8，IE9，Chrome+13，Opera11，FF5，Safari+5测试了上面的内容。|834478|更新2013年11月：|offset|length|style|BOLD|834479|下面是我目前使用的代码。我仍然必须支持IE8，所以我无法摆脱第一部分。事实证明，Android上的浏览器使用内置的Android下载管理器，并且无法以标准的方式可靠地解析文件名。|834480|string+contentDisposition;
if+(Request.Browser.Browser+==+"IE"+&&+(Request.Browser.Version+==+"7.0"+%7C%7C+Request.Browser.Version+==+"8.0"))
++++contentDisposition+=+"attachment;+filename="+%2B+Uri.EscapeDataString(fileName);
else+if+(Request.UserAgent+!=+null+&&+Request.UserAgent.ToLowerInvariant().Contains("android"))+//+android+built-in+download+manager+(all+browsers+on+android)
++++contentDisposition+=+"attachment;+filename=\""+%2B+MakeAndroidSafeFileName(fileName)+%2B+"\"";
else
++++contentDisposition+=+"attachment;+filename=\""+%2B+fileName+%2B+"\";+filename*=UTF-8''"+%2B+Uri.EscapeDataString(fileName);
Response.AddHeader("Content-Disposition",+contentDisposition);|834481|上面的测试现在在IE7-11，Chrome+32，Opera+12，FF25，Safari+6中测试，使用这个文件名下载:你好你好;.txt。|834482|在IE7上，它适用于某些字符，但不是所有字符。但是现在谁会关心IE7呢？|834483|这是我用来为Android生成安全文件名的函数。请注意，我不知道Android支持哪些字符，但我已经测试了这些字符是否有效：|834484|private+static+readonly+Dictionary<char,+char>+AndroidAllowedChars+=+"abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ._-%2B,@£$€!½§~'=()[]{}0123456789".ToDictionary(c+=>+c);
private+string+MakeAndroidSafeFileName(string+fileName)
{
++++char[]+newFileName+=+fileName.ToCharArray();
++++for+(int+i+=+0;+i+<+newFileName.Length;+i%2B%2B)
++++{
++++++++if+(!AndroidAllowedChars.ContainsKey(newFileName[i]))
++++++++++++newFileName[i]+=+'_';
++++}
++++return+new+string(newFileName);
}|834485|@TomZ:我在IE7和IE8中进行了测试，结果证明我不需要逃避撇号(')。你有一个失败的例子吗？|834486|@：按照RFC6266的说法，将两个文件名组合在一行上，除了安卓和IE7%2B8之外，我已经更新了代码以反映这一点。谢谢你的建议。|834487|@Thilo:对GoodReader或其他非浏览器一无所知。使用Android方法可能会有一些运气。|834488|@亚历克斯·朱科夫斯基:我不知道为什么，但正如在连接上讨论过的，它似乎工作得不太好。|834489|entityMap|0|LINK|mutability|MUTABLE|url|https://connect.microsoft.com/IE/feedback/details/820435/ie-11-does-not-support-decoding-the-filename-parameter-of-content-disposition-http-header-when-using-mime-encoded-word-syntax-generated-by-an-asp-net-handler^0|0|0|0|0|0|0|0|0|0|0|2|0|0|0|0|0|0|0|0|0|0|O|2|0|0^^$0|@$1|2|3|4|5|6|7|1S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|1T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|1U|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|1V|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|1W|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|1X|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|1Y|8|@]|9|@]|A|$]]|$1|Q|3|R|5|D|7|1Z|8|@]|9|@]|A|$E|F]]|$1|S|3|T|5|6|7|20|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|21|8|@$W|22|X|23|Y|Z]]|9|@]|A|$]]|$1|10|3|11|5|6|7|24|8|@]|9|@]|A|$]]|$1|12|3|13|5|D|7|25|8|@]|9|@]|A|$E|F]]|$1|14|3|15|5|6|7|26|8|@]|9|@]|A|$]]|$1|16|3|17|5|6|7|27|8|@]|9|@]|A|$]]|$1|18|3|19|5|6|7|28|8|@]|9|@]|A|$]]|$1|1A|3|1B|5|D|7|29|8|@]|9|@]|A|$E|F]]|$1|1C|3|1D|5|6|7|2A|8|@]|9|@]|A|$]]|$1|1E|3|1F|5|6|7|2B|8|@]|9|@]|A|$]]|$1|1G|3|1H|5|6|7|2C|8|@]|9|@]|A|$]]|$1|1I|3|1J|5|6|7|2D|8|@]|9|@$W|2E|X|2F|1|2G]]|A|$]]|$1|1K|3|-4|5|6|7|2H|8|@]|9|@]|A|$]]]|1L|$1M|$5|1N|1O|1P|A|$1Q|1R]]]]

I know this is an old post but it is still very relevant. I have found that modern browsers support rfc5987, which allows utf-8 encoding, percentage encoded (url-encoded). Then Naïve file.txt becomes:

<pre><code>Content-Disposition: attachment; filename*=UTF-8''Na%C3%AFve%20file.txt
</code></pre>

Safari (5) does not support this. Instead you should use the Safari standard of writing the file name directly in your utf-8 encoded header:

<pre><code>Content-Disposition: attachment; filename=Naïve file.txt
</code></pre>

IE8 and older don't support it either and you need to use the IE standard of utf-8 encoding, percentage encoded:

<pre><code>Content-Disposition: attachment; filename=Na%C3%AFve%20file.txt
</code></pre>

In ASP.Net I use the following code:

<pre class="lang-cs prettyprint-override"><code>string contentDisposition;
if (Request.Browser.Browser == "IE" &amp;&amp; (Request.Browser.Version == "7.0" || Request.Browser.Version == "8.0"))
 contentDisposition = "attachment; filename=" + Uri.EscapeDataString(fileName);
else if (Request.Browser.Browser == "Safari")
 contentDisposition = "attachment; filename=" + fileName;
else
 contentDisposition = "attachment; filename*=UTF-8''" + Uri.EscapeDataString(fileName);
Response.AddHeader("Content-Disposition", contentDisposition);
</code></pre>

I tested the above using IE7, IE8, IE9, Chrome 13, Opera 11, FF5, Safari 5.

Update November 2013:

Here is the code I currently use. I still have to support IE8, so I cannot get rid of the first part. It turns out that browsers on Android use the built in Android download manager and it cannot reliably parse file names in the standard way.

<pre class="lang-cs prettyprint-override"><code>string contentDisposition;
if (Request.Browser.Browser == "IE" &amp;&amp; (Request.Browser.Version == "7.0" || Request.Browser.Version == "8.0"))
 contentDisposition = "attachment; filename=" + Uri.EscapeDataString(fileName);
else if (Request.UserAgent != null &amp;&amp; Request.UserAgent.ToLowerInvariant().Contains("android")) // android built-in download manager (all browsers on android)
 contentDisposition = "attachment; filename=\"" + MakeAndroidSafeFileName(fileName) + "\"";
else
 contentDisposition = "attachment; filename=\"" + fileName + "\"; filename*=UTF-8''" + Uri.EscapeDataString(fileName);
Response.AddHeader("Content-Disposition", contentDisposition);
</code></pre>

The above now tested in IE7-11, Chrome 32, Opera 12, FF25, Safari 6, using this filename for download: 你好abcABCæøåÆØÅäöüïëêîâéíáóúýñ½§!#¤%&amp;()=`@£$€{[]}+´¨^~'-_,;.txt

On IE7 it works for some characters but not all. But who cares about IE7 nowadays?

This is the function I use to generate safe file names for Android. Note that I don't know which characters are supported on Android but that I have tested that these work for sure:

<pre class="lang-cs prettyprint-override"><code>private static readonly Dictionary&lt;char, char&gt; AndroidAllowedChars = "abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ._-+,@£$€!½§~'=()[]{}0123456789".ToDictionary(c =&gt; c);
private string MakeAndroidSafeFileName(string fileName)
{
 char[] newFileName = fileName.ToCharArray();
 for (int i = 0; i &lt; newFileName.Length; i++)
 {
 if (!AndroidAllowedChars.ContainsKey(newFileName[i]))
 newFileName[i] = '_';
 }
 return new string(newFileName);
}
</code></pre>

@TomZ: I tested in IE7 and IE8 and it turned out that I did not need to escape apostrophe ('). Do you have an example where it fails?

@Dave Van den Eynde: Combining the two file names on one line as according to RFC6266 works except for Android and IE7+8 and I have updated the code to reflect this. Thank you for the suggestion.

@Thilo: No idea about GoodReader or any other non-browser. You might have some luck using the Android approach.

@Alex Zhukovskiy: I don't know why but as discussed on <a href="https://connect.microsoft.com/IE/feedback/details/820435/ie-11-does-not-support-decoding-the-filename-parameter-of-content-disposition-http-header-when-using-mime-encoded-word-syntax-generated-by-an-asp-net-handler" rel="noreferrer" title="Connect">Connect</a> it doesn't seem to work terribly well.

blocks|key|1135191|text|我在所有主要浏览器中测试了以下代码，包括旧的Explorer(通过兼容性模式)，它在任何地方都工作得很好：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1135192|$filename+=+$_GET['file'];+//this+string+from+$_GET+is+already+decoded
if+(strstr($_SERVER['HTTP_USER_AGENT'],"MSIE"))
++$filename+=+rawurlencode($filename);
header('Content-Disposition:+attachment;+filename="'.$filename.'"');|code-block|syntax|javascript|1135193|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I tested the following code in all major browsers, including older Explorers (via the compatibility mode), and it works well everywhere:

<pre class="lang-php prettyprint-override"><code>$filename = $_GET['file']; //this string from $_GET is already decoded
if (strstr($_SERVER['HTTP_USER_AGENT'],"MSIE"))
 $filename = rawurlencode($filename);
header('Content-Disposition: attachment; filename="'.$filename.'"');
</code></pre>

blocks|key|834502|text|我使用以下代码片段进行编码(假设fileName包含文件的文件名和扩展名，即:+test.txt)：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|834503|PHP：|834504|if+(+strpos+(+$_SERVER+[+'HTTP_USER_AGENT'+],+"MSIE"+)+>+0+)
{
+++++header+(+'Content-Disposition:+attachment;+filename="'+.+rawurlencode+(+$fileName+)+.+'"'+);
}
else
{
+++++header(+'Content-Disposition:+attachment;+filename*=UTF-8\'\''+.+rawurlencode+(+$fileName+)+);
}|code-block|syntax|javascript|834505|爪哇：|834506|fileName+=+request.getHeader+(+"user-agent"+).contains+(+"MSIE"+)+?+URLEncoder.encode+(+fileName,+"utf-8")+:+MimeUtility.encodeWord+(+fileName+);
response.setHeader+(+"Content-disposition",+"attachment;+filename=\""+%2B+fileName+%2B+"\"");|834507|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

I use the following code snippets for encoding (assuming fileName contains the filename and extension of the file, i.e.: test.txt):

<hr>

PHP:

<pre class="lang-php prettyprint-override"><code>if ( strpos ( $_SERVER [ 'HTTP_USER_AGENT' ], "MSIE" ) &gt; 0 )
{
 header ( 'Content-Disposition: attachment; filename="' . rawurlencode ( $fileName ) . '"' );
}
else
{
 header( 'Content-Disposition: attachment; filename*=UTF-8\'\'' . rawurlencode ( $fileName ) );
}
</code></pre>

Java:

<pre class="lang-java prettyprint-override"><code>fileName = request.getHeader ( "user-agent" ).contains ( "MSIE" ) ? URLEncoder.encode ( fileName, "utf-8") : MimeUtility.encodeWord ( fileName );
response.setHeader ( "Content-disposition", "attachment; filename=\"" + fileName + "\"");
</code></pre>

blocks|key|834567|text|RFC+6266描述了“超文本传输协议(HTTP)中内容处理头字段的使用”。引证如下：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|834568|6.国际化考虑
“filename*”参数(第4.3节)使用[RFC5987]中定义的编码，允许服务器在ISO-8859-1字符集之外传输字符，还可以选择指定所使用的语言。|blockquote|style|CODE|834569|在他们的示例部分里|834570|此示例与上面的示例相同，但为了与未实现RFC+5987的用户代理兼容，添加了"filename“参数：
内容处理:附件；filename=“欧元利率”；文件名*=utf-8‘’%25e2%2582%25ac%2520
注意:那些不支持RFC+5987编码的用户代理在“filename”之后出现时忽略“filename*”。|834571|在附录D中，还有一长串增加互操作性的建议。它还指出了比较实现的站点。当前适用于常见文件名的所有通过测试包括：|834572|不平原区：普通的ISO-8859-1文件名，带有双引号，没有编码.这需要一个文件名，该文件名为所有ISO-8859-1，并且不包含百分比符号，至少在十六进制数字前面不包含。|unordered-list-item|834573|阿特夫纳：按上述顺序排列的两个参数。虽然IE8将使用“filename”参数，但大多数浏览器上的大多数文件名都可以使用。|834574|该RFC+5987依次引用RFC+2231，后者描述实际的格式。2231主要用于邮件，5987也告诉我们HTTP报头可以使用哪些部分。不要将其与在multipart/form-data+HTTP主体中使用的MIME标头混淆，后者由RFC+2388+(特别是第4.4节)和HTML+5草稿管理。|834575|entityMap|0|LINK|mutability|MUTABLE|url|https://www.rfc-editor.org/rfc/rfc6266|1|https://www.rfc-editor.org/rfc/rfc6266#section-6|2|https://www.rfc-editor.org/rfc/rfc6266#section-4.3|3|https://www.rfc-editor.org/rfc/rfc5987|4|https://www.rfc-editor.org/rfc/rfc6266#section-5|5|6|7|https://www.rfc-editor.org/rfc/rfc6266#appendix-D|8|http://greenbytes.de/tech/tc2231/|9|http://greenbytes.de/tech/tc2231/#attwithisofnplain|10|http://greenbytes.de/tech/tc2231/#attfnboth|11|12|https://www.rfc-editor.org/rfc/rfc2231|13|https://www.rfc-editor.org/rfc/rfc2388|14|https://www.rfc-editor.org/rfc/rfc2388#section-4.4|15|http://www.w3.org/TR/html51/forms.html#multipart-form-data^0|0|8|0|0|9|9|0|7|1|M|5|2|V|7|3|0|4|4|4|0|3I|8|3Z|9|J|8|5|31|8|6|0|1|3|7|Q|7|8|0|0|4|9|0|R|8|0|4|A|0|21|J|1|8|B|D|8|C|37|8|D|3K|5|E|3R|8|F|0^^$0|@$1|2|3|4|5|6|7|1U|8|@]|9|@$A|1V|B|1W|1|1X]]|C|$]]|$1|D|3|E|5|F|7|1Y|8|@$A|1Z|B|20|G|H]]|9|@$A|21|B|22|1|23]|$A|24|B|25|1|26]|$A|27|B|28|1|29]]|C|$]]|$1|I|3|J|5|6|7|2A|8|@]|9|@$A|2B|B|2C|1|2D]]|C|$]]|$1|K|3|L|5|F|7|2E|8|@$A|2F|B|2G|G|H]|$A|2H|B|2I|G|H]]|9|@$A|2J|B|2K|1|2L]|$A|2M|B|2N|1|2O]]|C|$]]|$1|M|3|N|5|6|7|2P|8|@]|9|@$A|2Q|B|2R|1|2S]|$A|2T|B|2U|1|2V]]|C|$]]|$1|O|3|P|5|Q|7|2W|8|@]|9|@$A|2X|B|2Y|1|2Z]]|C|$]]|$1|R|3|S|5|Q|7|30|8|@$A|31|B|32|G|H]]|9|@$A|33|B|34|1|35]]|C|$]]|$1|T|3|U|5|6|7|36|8|@$A|37|B|38|G|H]]|9|@$A|39|B|3A|1|3B]|$A|3C|B|3D|1|3E]|$A|3F|B|3G|1|3H]|$A|3I|B|3J|1|3K]|$A|3L|B|3M|1|3N]]|C|$]]|$1|V|3|-4|5|6|7|3O|8|@]|9|@]|C|$]]]|W|$X|$5|Y|Z|10|C|$11|12]]|13|$5|Y|Z|10|C|$11|14]]|15|$5|Y|Z|10|C|$11|16]]|17|$5|Y|Z|10|C|$11|18]]|19|$5|Y|Z|10|C|$11|1A]]|1B|$5|Y|Z|10|C|$11|18]]|1C|$5|Y|Z|10|C|$11|18]]|1D|$5|Y|Z|10|C|$11|1E]]|1F|$5|Y|Z|10|C|$11|1G]]|1H|$5|Y|Z|10|C|$11|1I]]|1J|$5|Y|Z|10|C|$11|1K]]|1L|$5|Y|Z|10|C|$11|18]]|1M|$5|Y|Z|10|C|$11|1N]]|1O|$5|Y|Z|10|C|$11|1P]]|1Q|$5|Y|Z|10|C|$11|1R]]|1S|$5|Y|Z|10|C|$11|1T]]]]

<a href="https://www.rfc-editor.org/rfc/rfc6266" rel="nofollow noreferrer">RFC 6266</a> describes the “Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)”. Quoting from that:
<blockquote>
<a href="https://www.rfc-editor.org/rfc/rfc6266#section-6" rel="nofollow noreferrer">6. Internationalization Considerations</a>
The “<code>filename*</code>” parameter (<a href="https://www.rfc-editor.org/rfc/rfc6266#section-4.3" rel="nofollow noreferrer">Section 4.3</a>), using the encoding defined
in [<a href="https://www.rfc-editor.org/rfc/rfc5987" rel="nofollow noreferrer">RFC5987</a>], allows the server to transmit characters outside the
ISO-8859-1 character set, and also to optionally specify the language
in use.
</blockquote>
And in their <a href="https://www.rfc-editor.org/rfc/rfc6266#section-5" rel="nofollow noreferrer">examples section</a>:
<blockquote>
This example is the same as the one above, but adding the &quot;filename&quot;
parameter for compatibility with user agents not implementing
<a href="https://www.rfc-editor.org/rfc/rfc5987" rel="nofollow noreferrer">RFC 5987</a>:
<pre><code>Content-Disposition: attachment;
 filename=&quot;EURO rates&quot;;
 filename*=utf-8''%e2%82%ac%20rates
</code></pre>
Note: Those user agents that do not support the <a href="https://www.rfc-editor.org/rfc/rfc5987" rel="nofollow noreferrer">RFC 5987</a> encoding
ignore “<code>filename*</code>” when it occurs after “<code>filename</code>”.
</blockquote>
In <a href="https://www.rfc-editor.org/rfc/rfc6266#appendix-D" rel="nofollow noreferrer">Appendix D</a> there is also a long list of suggestions to increase interoperability. It also points at <a href="http://greenbytes.de/tech/tc2231/" rel="nofollow noreferrer">a site which compares implementations</a>. Current all-pass tests suitable for common file names include:
<ul>
<li><a href="http://greenbytes.de/tech/tc2231/#attwithisofnplain" rel="nofollow noreferrer">attwithisofnplain</a>: plain ISO-8859-1 file name with double quotes and without encoding. This requires a file name which is all ISO-8859-1 and does not contain percent signs, at least not in front of hex digits.</li>
<li><a href="http://greenbytes.de/tech/tc2231/#attfnboth" rel="nofollow noreferrer">attfnboth</a>: two parameters in the order described above. Should work for most file names on most browsers, although IE8 will use the “<code>filename</code>” parameter.</li>
</ul>
That <a href="https://www.rfc-editor.org/rfc/rfc5987" rel="nofollow noreferrer">RFC 5987</a> in turn references <a href="https://www.rfc-editor.org/rfc/rfc2231" rel="nofollow noreferrer">RFC 2231</a>, which describes the actual format. 2231 is primarily for mail, and 5987 tells us what parts may be used for HTTP headers as well. Don't confuse this with MIME headers used inside a <code>multipart/form-data</code> HTTP body, which is governed by <a href="https://www.rfc-editor.org/rfc/rfc2388" rel="nofollow noreferrer">RFC 2388</a> (<a href="https://www.rfc-editor.org/rfc/rfc2388#section-4.4" rel="nofollow noreferrer">section 4.4</a> in particular) and the <a href="http://www.w3.org/TR/html51/forms.html#multipart-form-data" rel="nofollow noreferrer">HTML 5 draft</a>.

blocks|key|1135454|text|我们在一个web应用程序中遇到了类似的问题，最后从HTML+<input+type="file">读取文件名，并在一个新的<input+type="hidden">中以url编码的形式设置文件名。当然，我们必须删除一些浏览器返回的路径，比如“C：\fakepath”。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1135455|当然，这并不能直接回答OPs的问题，但对其他人来说可能是一个解决方案。|1135456|entityMap^0|U|J|1P|L|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|P|8|@]|D|@]|E|$]]]|I|$]]

We had a similar problem in a web application, and ended up by reading the filename from the HTML <code>&lt;input type="file"&gt;</code>, and setting that in the url-encoded form in a new HTML <code>&lt;input type="hidden"&gt;</code>. Of course we had to remove the path like "C:\fakepath\" that is returned by some browsers. 

Of course this does not directly answer OPs question, but may be a solution for others.

blocks|key|1135490|text|最后，我在我的"download.php“脚本中(基于这个博客和这些测试用例)编写了以下代码。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1135491|$il1_filename+=+utf8_decode($filename);
$to_underscore+=+"\"\\#*;:%7C<>/?";
$safe_filename+=+strtr($il1_filename,+$to_underscore,+str_repeat("_",+strlen($to_underscore)));

header("Content-Disposition:+attachment;+filename=\"$safe_filename\""
.(+$safe_filename+===+$filename+?+""+:+";+filename*=UTF-8''".rawurlencode($filename)+));|code-block|syntax|javascript|1135492|这使用了filename=的标准方式“.”只要只使用iso+latin1+1和“安全”字符，它就会添加文件名*=utf-8‘url编码方式。根据这个特定的测试用例，它应该从MSIE9向上工作，在最近的FF，Chrome，Safari上；在较低的MSIE版本上，它应该提供包含文件名的it+8859-1版本的文件名，并在这个编码中的字符上加上下划线。|1135493|最后注:最大。apache上每个标头字段的大小为8190字节。UTF-8可以达到每个字符4个字节；在rawurlencode之后，它是x3+=每一个字符12字节。相当低效，但理论上仍有可能在文件名中有超过600个“微笑”%25F0%259F%2598%2581。|1135494|entityMap|0|LINK|mutability|MUTABLE|url|http://www.bennadel.com/blog/2591-embedding-foreign-characters-in-your-content-disposition-filename-header.htm|1|http://greenbytes.de/tech/tc2231/|2|http://greenbytes.de/tech/tc2231/#attwithfn2231utf8^0|R|4|0|W|6|1|0|0|20|9|2|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@$A|Z|B|10|1|11]|$A|12|B|13|1|14]]|C|$]]|$1|D|3|E|5|F|7|15|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|16|8|@]|9|@$A|17|B|18|1|19]]|C|$]]|$1|K|3|L|5|6|7|1A|8|@]|9|@]|C|$]]|$1|M|3|-4|5|6|7|1B|8|@]|9|@]|C|$]]]|N|$O|$5|P|Q|R|C|$S|T]]|U|$5|P|Q|R|C|$S|V]]|W|$5|P|Q|R|C|$S|X]]]]

I ended up with the following code in my "download.php" script (based on <a href="http://www.bennadel.com/blog/2591-embedding-foreign-characters-in-your-content-disposition-filename-header.htm" rel="nofollow noreferrer">this blogpost</a> and <a href="http://greenbytes.de/tech/tc2231/" rel="nofollow noreferrer">these test cases</a>).

<pre><code>$il1_filename = utf8_decode($filename);
$to_underscore = "\"\\#*;:|&lt;&gt;/?";
$safe_filename = strtr($il1_filename, $to_underscore, str_repeat("_", strlen($to_underscore)));

header("Content-Disposition: attachment; filename=\"$safe_filename\""
.( $safe_filename === $filename ? "" : "; filename*=UTF-8''".rawurlencode($filename) ));
</code></pre>

This uses the standard way of filename="..." as long as there are only iso-latin1 and "safe" characters used; if not, it adds the filename*=UTF-8'' url-encoded way. According to <a href="http://greenbytes.de/tech/tc2231/#attwithfn2231utf8" rel="nofollow noreferrer">this specific test case</a>, it should work from MSIE9 up, and on recent FF, Chrome, Safari; on lower MSIE version, it should offer filename containing the ISO8859-1 version of the filename, with underscores on characters not in this encoding.

Final note: the max. size for each header field is 8190 bytes on apache. UTF-8 can be up to four bytes per character; after rawurlencode, it is x3 = 12 bytes per one character. Pretty inefficient, but it should still be theoretically possible to have more than 600 "smiles" %F0%9F%98%81 in the filename.

blocks|key|834720|text|在ASP.NET+Web中，我对文件名进行了编码：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|834721|public+static+class+HttpRequestMessageExtensions
{
++++public+static+HttpResponseMessage+CreateFileResponse(this+HttpRequestMessage+request,+byte[]+data,+string+filename,+string+mediaType)
++++{
++++++++HttpResponseMessage+response+=+new+HttpResponseMessage(HttpStatusCode.OK);
++++++++var+stream+=+new+MemoryStream(data);
++++++++stream.Position+=+0;

++++++++response.Content+=+new+StreamContent(stream);

++++++++response.Content.Headers.ContentType+=+
++++++++++++new+MediaTypeHeaderValue(mediaType);

++++++++//+URL-Encode+filename
++++++++//+Fixes+behavior+in+IE,+that+filenames+with+non+US-ASCII+characters
++++++++//+stay+correct+(not+"_utf-8_.......=_=").
++++++++var+encodedFilename+=+HttpUtility.UrlEncode(filename,+Encoding.UTF8);

++++++++response.Content.Headers.ContentDisposition+=
++++++++++++new+ContentDispositionHeaderValue("attachment")+{+FileName+=+encodedFilename+};
++++++++return+response;
++++}
}|code-block|syntax|javascript|834722|​|834723|📷|atomic|offset|length|834724|834725|834726|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/7890ffe3f6fbd0bf1126037dbbdf47f3.jpg|imageAlt|1|https://developer.qcloudimg.com/http-save/yehe-900000/f8bbd6901cb361db0966e74cf3c245ac.jpg^0|0|0|0|0|1|0|0|0|1|1|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|12|8|@]|9|@]|A|$]]|$1|I|3|J|5|K|7|13|8|@]|9|@$L|14|M|15|1|16]]|A|$]]|$1|N|3|J|5|K|7|17|8|@]|9|@$L|18|M|19|1|1A]]|A|$]]|$1|O|3|H|5|6|7|1B|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]]|Q|$R|$5|S|T|U|A|$V|W|X|-4]]|Y|$5|S|T|U|A|$V|Z|X|-4]]]]

In ASP.NET Web API, I url encode the filename:

<pre><code>public static class HttpRequestMessageExtensions
{
 public static HttpResponseMessage CreateFileResponse(this HttpRequestMessage request, byte[] data, string filename, string mediaType)
 {
 HttpResponseMessage response = new HttpResponseMessage(HttpStatusCode.OK);
 var stream = new MemoryStream(data);
 stream.Position = 0;

 response.Content = new StreamContent(stream);

 response.Content.Headers.ContentType = 
 new MediaTypeHeaderValue(mediaType);

 // URL-Encode filename
 // Fixes behavior in IE, that filenames with non US-ASCII characters
 // stay correct (not "_utf-8_.......=_=").
 var encodedFilename = HttpUtility.UrlEncode(filename, Encoding.UTF8);

 response.Content.Headers.ContentDisposition =
 new ContentDispositionHeaderValue("attachment") { FileName = encodedFilename };
 return response;
 }
}
</code></pre>

<img src="https://i.stack.imgur.com/Fsla4.jpg" alt="IE 9 Not fixed"> 
<img src="https://i.stack.imgur.com/50Ako.jpg" alt="IE 9 Fixed">

blocks|key|1135696|text|将文件名放在双引号中。帮我解决了这个问题。如下所示：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1135697|Content-Disposition:+attachment;+filename="My+Report.doc"|code-block|syntax|javascript|1135698|下载|offset|length|1135699|我测试过多种选择。浏览器不支持规格和行为不同，我相信双引号是最好的选择。|1135700|entityMap|0|LINK|mutability|MUTABLE|url|http://kb.mozillazine.org/Filenames_with_spaces_are_truncated_upon_download^0|0|0|0|2|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@]|9|@$I|X|J|Y|1|Z]]|A|$]]|$1|K|3|L|5|6|7|10|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]]]

Put the file name in double quotes. Solved the problem for me. Like this:

<pre><code>Content-Disposition: attachment; filename="My Report.doc"
</code></pre>

<a href="http://kb.mozillazine.org/Filenames_with_spaces_are_truncated_upon_download" rel="nofollow noreferrer">http://kb.mozillazine.org/Filenames_with_spaces_are_truncated_upon_download</a>

I've tested multiple options. Browsers do not support the specs and act differently, I believe double quotes is the best option.

blocks|key|1135718|text|如果您使用的是nodejs后端，可以使用下面的代码，我找到了这里|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1135719|var+fileName+=+'my+file(2).txt';
var+header+=+"Content-Disposition:+attachment;+filename*=UTF-8''"+
+++++++++++++%2B+encodeRFC5987ValueChars(fileName);

function+encodeRFC5987ValueChars+(str)+{
++++return+encodeURIComponent(str).
++++++++//+Note+that+although+RFC3986+reserves+"!",+RFC5987+does+not,
++++++++//+so+we+do+not+need+to+escape+it
++++++++replace(/['()]/g,+escape).+//+i.e.,+%2527+%2528+%2529
++++++++replace(/\*/g,+'%252A').
++++++++++++//+The+following+are+not+required+for+percent-encoding+per+RFC5987,+
++++++++++++//+so+we+can+allow+for+a+little+better+readability+over+the+wire:+%7C`%5E
++++++++++++replace(/%25(?:7C%7C60%7C5E)/g,+unescape);
}|code-block|syntax|javascript|1135720|entityMap|0|LINK|mutability|MUTABLE|url|https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/encodeURIComponent%2523Examples^0|U|2|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]]|C|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|C|$G|H]]|$1|I|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]]]

If you are using a nodejs backend you can use the following code I found <a href="https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/encodeURIComponent%23Examples" rel="nofollow">here</a>

<pre class="lang-js prettyprint-override"><code>var fileName = 'my file(2).txt';
var header = "Content-Disposition: attachment; filename*=UTF-8''" 
 + encodeRFC5987ValueChars(fileName);

function encodeRFC5987ValueChars (str) {
 return encodeURIComponent(str).
 // Note that although RFC3986 reserves "!", RFC5987 does not,
 // so we do not need to escape it
 replace(/['()]/g, escape). // i.e., %27 %28 %29
 replace(/\*/g, '%2A').
 // The following are not required for percent-encoding per RFC5987, 
 // so we can allow for a little better readability over the wire: |`^
 replace(/%(?:7C|60|5E)/g, unescape);
}
</code></pre>

blocks|key|1135726|text|在PHP中，这样做是为了我(假设文件名是UTF8编码的)：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1135727|header('Content-Disposition:+attachment;'
++++.+'filename="'+.+addslashes(utf8_decode($filename))+.+'";'
++++.+'filename*=utf-8\'\''+.+rawurlencode($filename));|code-block|syntax|javascript|1135728|测试的IE8-11，火狐和Chrome。|1135729|如果浏览器能够解释文件名*=utf-8，它将使用文件名的UTF8版本，否则它将使用已解码的文件名。如果您的文件名包含无法用ISO8859-1表示的字符，您可能需要考虑使用iconv。|offset|length|style|CODE|1135730|entityMap^0|0|0|0|2D|5|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|T|8|@$K|U|L|V|M|N]]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

In PHP this did it for me (assuming the filename is UTF8 encoded):

<pre><code>header('Content-Disposition: attachment;'
 . 'filename="' . addslashes(utf8_decode($filename)) . '";'
 . 'filename*=utf-8\'\'' . rawurlencode($filename));
</code></pre>

Tested against IE8-11, Firefox and Chrome. 
If the browser can interpret filename*=utf-8 it will use the UTF8 version of the filename, else it will use the decoded filename. If your filename contains characters that can't be represented in ISO-8859-1 you might want to consider using <code>iconv</code> instead.

blocks|key|834785|text|经典ASP解决方案|type|unstyled|depth|inlineStyleRanges|entityRanges|data|834786|大多数现代浏览器现在都支持将Filename作为UTF-8传递，但正如我使用的基于FreeASPUpload.Net的文件上传解决方案(站点不再存在，链接指向http://archive.org/web/)一样，它无法工作，因为二进制的解析依赖于读取单个字节的ASCII编码字符串，当您传递UTF-8编码数据时，这种解析工作很好，直到您到达字符ASCII为止。|offset|length|style|CODE|834787|但是，我找到了一种解决方案，可以让代码以UTF-8的形式读取和解析二进制文件。|834788|Public+Function+BytesToString(bytes)++++'UTF-8..
++Dim+bslen
++Dim+i,+k+,+N+
++Dim+b+,+count+
++Dim+str

++bslen+=+LenB(bytes)
++str=""

++i+=+0
++Do+While+i+<+bslen
++++b+=+AscB(MidB(bytes,i%2B1,1))

++++If+(b+And+&HFC)+=+&HFC+Then
++++++count+=+6
++++++N+=+b+And+&H1
++++ElseIf+(b+And+&HF8)+=+&HF8+Then
++++++count+=+5
++++++N+=+b+And+&H3
++++ElseIf+(b+And+&HF0)+=+&HF0+Then
++++++count+=+4
++++++N+=+b+And+&H7
++++ElseIf+(b+And+&HE0)+=+&HE0+Then
++++++count+=+3
++++++N+=+b+And+&HF
++++ElseIf+(b+And+&HC0)+=+&HC0+Then
++++++count+=+2
++++++N+=+b+And+&H1F
++++Else
++++++count+=+1
++++++str+=+str+&+Chr(b)
++++End+If

++++If+i+%2B+count+-+1+>+bslen+Then
++++++str+=+str&"?"
++++++Exit+Do
++++End+If

++++If+count>1+then
++++++For+k+=+1+To+count+-+1
++++++++b+=+AscB(MidB(bytes,i%2Bk%2B1,1))
++++++++N+=+N+*+&H40+%2B+(b+And+&H3F)
++++++Next
++++++str+=+str+&+ChrW(N)
++++End+If
++++i+=+i+%2B+count
++Loop

++BytesToString+=+str
End+Function|code-block|syntax|javascript|834789|通过在我自己的代码中实现来自纯ASP文件上传的BytesToString()函数，可以使UTF-8文件名正常工作。|834790|有用的链接|834791|ASP经典应用程序中的多部分/表单数据和UTF-8|unordered-list-item|834792|Unicode，UTF，ASCII，ANSI格式差异|834793|entityMap|0|LINK|mutability|MUTABLE|url|http://web.archive.org/web/20140614223449/http://www.freeaspupload.net/|1|http://archive.org/web/|2|http://aspuploader.com/default.html|3|https://stackoverflow.com/a/1715014/692942|4|https://stackoverflow.com/a/700221/692942^0|0|E|8|O|5|15|H|0|27|N|1|0|0|0|N|F|18|5|E|8|2|0|0|0|P|3|0|0|Q|4|0^^$0|@$1|2|3|4|5|6|7|1D|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1E|8|@$D|1F|E|1G|F|G]|$D|1H|E|1I|F|G]]|9|@$D|1J|E|1K|1|1L]|$D|1M|E|1N|1|1O]]|A|$]]|$1|H|3|I|5|6|7|1P|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|1Q|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|1R|8|@$D|1S|E|1T|F|G]|$D|1U|E|1V|F|G]]|9|@$D|1W|E|1X|1|1Y]]|A|$]]|$1|Q|3|R|5|6|7|1Z|8|@]|9|@]|A|$]]|$1|S|3|T|5|U|7|20|8|@]|9|@$D|21|E|22|1|23]]|A|$]]|$1|V|3|W|5|U|7|24|8|@]|9|@$D|25|E|26|1|27]]|A|$]]|$1|X|3|-4|5|6|7|28|8|@]|9|@]|A|$]]]|Y|$Z|$5|10|11|12|A|$13|14]]|15|$5|10|11|12|A|$13|16]]|17|$5|10|11|12|A|$13|18]]|19|$5|10|11|12|A|$13|1A]]|1B|$5|10|11|12|A|$13|1C]]]]

<h3>Classic ASP Solution</h3>
Most modern browsers support passing the <code>Filename</code> as <code>UTF-8</code> now but as was the case with a File Upload solution I use that was based on <a href="http://web.archive.org/web/20140614223449/http://www.freeaspupload.net/" rel="nofollow noreferrer">FreeASPUpload.Net</a> (site no longer exists, link points to <a href="http://archive.org/web/" rel="nofollow noreferrer">archive.org</a>) it wouldn't work as the parsing of the binary relied on reading single byte ASCII encoded strings, which worked fine when you passed UTF-8 encoded data until you get to characters ASCII doesn't support.
However I was able to find a solution to get the code to read and parse the binary as UTF-8.
<pre class="lang-vb prettyprint-override"><code>Public Function BytesToString(bytes) 'UTF-8..
 Dim bslen
 Dim i, k , N 
 Dim b , count 
 Dim str

 bslen = LenB(bytes)
 str=&quot;&quot;

 i = 0
 Do While i &lt; bslen
 b = AscB(MidB(bytes,i+1,1))

 If (b And &amp;HFC) = &amp;HFC Then
 count = 6
 N = b And &amp;H1
 ElseIf (b And &amp;HF8) = &amp;HF8 Then
 count = 5
 N = b And &amp;H3
 ElseIf (b And &amp;HF0) = &amp;HF0 Then
 count = 4
 N = b And &amp;H7
 ElseIf (b And &amp;HE0) = &amp;HE0 Then
 count = 3
 N = b And &amp;HF
 ElseIf (b And &amp;HC0) = &amp;HC0 Then
 count = 2
 N = b And &amp;H1F
 Else
 count = 1
 str = str &amp; Chr(b)
 End If

 If i + count - 1 &gt; bslen Then
 str = str&amp;&quot;?&quot;
 Exit Do
 End If

 If count&gt;1 then
 For k = 1 To count - 1
 b = AscB(MidB(bytes,i+k+1,1))
 N = N * &amp;H40 + (b And &amp;H3F)
 Next
 str = str &amp; ChrW(N)
 End If
 i = i + count
 Loop

 BytesToString = str
End Function
</code></pre>
Credit goes to <a href="http://aspuploader.com/default.html" rel="nofollow noreferrer">Pure ASP File Upload</a> by implementing the <code>BytesToString()</code> function from <code>include_aspuploader.asp</code> in my own code I was able to get <code>UTF-8</code> filenames working.
<hr />
<h3>Useful Links</h3>
<ul>
<li><a href="https://stackoverflow.com/a/1715014/692942">Multipart/form-data and UTF-8 in a ASP Classic application</a>
</li>
<li><a href="https://stackoverflow.com/a/700221/692942">Unicode, UTF, ASCII, ANSI format differences</a>
</li>
</ul>

blocks|key|1135834|text|只是因为我今天尝试了所有的东西来回应客户的问题|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1135835|除了为日语配置的Safari之外，我们的客户测试的所有浏览器都在filename=text.pdf中工作得最好--其中的文本是ASP.Net/IIS在utf-8中序列化的一个客户值，没有url编码。出于某种原因，为英语配置的Safari将接受并正确保存一个以utf-8日文名称命名的文件，但为日语配置的同一浏览器将使用utf-8字符保存该文件。测试过的所有其他浏览器似乎工作得最好/很好(不管语言配置如何)，而文件名utf-8没有url编码。|unordered-list-item|1135836|我根本找不到一个实现not+5987/8187的浏览器。我用最新的Chrome，Firefox构建加上IE11和Edge进行了测试。我试着用文件名*=utf-8‘texturlencoded.pdf设置标题，并将其设置为两个filename=text.pdf；filename*=utf-8’texturlencoded.pdf。utf+5987/8187的任何一个功能在上面都没有得到正确的处理。|1135837|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|K|8|@]|9|@]|A|$]]|$1|G|3|-4|5|6|7|L|8|@]|9|@]|A|$]]]|H|$]]

Just an update since I was trying all this stuff today in response to a customer issue

<ul>
<li>With the exception of Safari configured for Japanese, all browsers our customer tested worked best with filename=text.pdf - where text is a customer value serialized by ASP.Net/IIS in utf-8 without url encoding. For some reason, Safari configured for English would accept and properly save a file with utf-8 Japanese name but that same browser configured for Japanese would save the file with the utf-8 chars uninterpreted. All other browsers tested seemed to work best/fine (regardless of language configuration) with the filename utf-8 encoded without url encoding.</li>
<li>I could not find a single browser implementing Rfc5987/8187 at all. I tested with the latest Chrome, Firefox builds plus IE 11 and Edge. I tried setting the header with just filename*=utf-8''texturlencoded.pdf, setting it with both filename=text.pdf; filename*=utf-8''texturlencoded.pdf. Not one feature of Rfc5987/8187 appeared to be getting processed correctly in any of the above.</li>
</ul>

blocks|key|1135865|text|4在$filenameFallback中有HeaderUtils::makeDisposition。您可以查看这个函数的细节-它类似于上面的答案。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1135866|用法示例：|1135867|$filenameFallback+=+preg_replace('#%5E.*\.#',+md5($filename)+.+'.',+$filename);
$disposition+=+$response->headers->makeDisposition(ResponseHeaderBag::DISPOSITION_ATTACHMENT,+$filename,+$filenameFallback);
$response->headers->set('Content-Disposition',+$disposition);|code-block|syntax|javascript|1135868|entityMap^0|2|H|L|S|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|T|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|U|8|@]|D|@]|E|$K|L]]|$1|M|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|N|$]]

PHP framework Symfony 4 has <code>$filenameFallback</code> in <code>HeaderUtils::makeDisposition</code>.
You can look into this function for details - it is similar to the answers above.

Usage example:

<pre><code>$filenameFallback = preg_replace('#^.*\.#', md5($filename) . '.', $filename);
$disposition = $response-&gt;headers-&gt;makeDisposition(ResponseHeaderBag::DISPOSITION_ATTACHMENT, $filename, $filenameFallback);
$response-&gt;headers-&gt;set('Content-Disposition', $disposition);
</code></pre>

blocks|key|1135898|text|从.NET+4.5+(和Core1.0)中，您可以使用ContentDispositionHeaderValue为您进行格式化。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1135899|var+fileName+=+"Naïve+file.txt";
var+h+=+new+System.Net.Http.Headers.ContentDispositionHeaderValue("attachment");
h.FileNameStar+=+fileName;
h.FileName+=+"fallback-ascii-name.txt";

Response.Headers.Add("Content-Disposition",+h.ToString());|code-block|syntax|javascript|1135900|h.ToString()将产生以下结果：|style|CODE|1135901|attachment;+filename*=utf-8''Na%25C3%25AFve%2520file.txt;+filename=fallback-ascii-name.txt|1135902|entityMap|0|LINK|mutability|MUTABLE|url|https://learn.microsoft.com/en-us/dotnet/api/system.net.http.headers.contentdispositionheadervalue^0|R|T|0|0|0|0|C|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@$A|X|B|Y|1|Z]]|C|$]]|$1|D|3|E|5|F|7|10|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|11|8|@$A|12|B|13|K|L]]|9|@]|C|$]]|$1|M|3|N|5|F|7|14|8|@]|9|@]|C|$G|H]]|$1|O|3|-4|5|6|7|15|8|@]|9|@]|C|$]]]|P|$Q|$5|R|S|T|C|$U|V]]]]

From .NET 4.5 (and Core 1.0) you can use <a href="https://learn.microsoft.com/en-us/dotnet/api/system.net.http.headers.contentdispositionheadervalue" rel="nofollow noreferrer">ContentDispositionHeaderValue</a> to do the formatting for you.
<pre class="lang-cs prettyprint-override"><code>var fileName = &quot;Naïve file.txt&quot;;
var h = new System.Net.Http.Headers.ContentDispositionHeaderValue(&quot;attachment&quot;);
h.FileNameStar = fileName;
h.FileName = &quot;fallback-ascii-name.txt&quot;;

Response.Headers.Add(&quot;Content-Disposition&quot;, h.ToString());
</code></pre>
<code>h.ToString()</code> Will result in:
<pre><code>attachment; filename*=utf-8''Na%C3%AFve%20file.txt; filename=fallback-ascii-name.txt
</code></pre>

blocks|key|1135927|text|对于那些需要JavaScript编码头的人，我发现这个函数工作得很好：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1135928|function+createContentDispositionHeader(filename:string)+{
++++const+encoded+=+encodeURIComponent(filename);
++++return+`attachment;+filename*=UTF-8''${encoded};+filename="${encoded}"`;
}|code-block|syntax|javascript|1135929|这是基于Nextcloud在下载文件时所做的事情。文件名首先显示为UTF-8编码，可能是为了与某些浏览器兼容，文件名也不带UTF-8前缀。|1135930|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

For those who need a JavaScript way of encoding the header, I found that this function works well:
<pre class="lang-js prettyprint-override"><code>function createContentDispositionHeader(filename:string) {
 const encoded = encodeURIComponent(filename);
 return `attachment; filename*=UTF-8''${encoded}; filename=&quot;${encoded}&quot;`;
}
</code></pre>
This is based on what Nextcloud seems to be doing when downloading a file. The filename appears first as UTF-8 encoded, and possibly for compatibility with some browsers, the filename also appears without the UTF-8 prefix.

blocks|key|137047|text|库类Unicode中的方法mimeHeaderEncode($string)执行此任务。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|137048|$file_name=+Unicode::mimeHeaderEncode($file_name);|code-block|syntax|javascript|137049|drupal/php中的示例：|137050|https://github.com/drupal/core-utility/blob/8.8.x/Unicode.php

/**
+++*+Encodes+MIME/HTTP+headers+that+contain+incorrectly+encoded+characters.
+++*
+++*+For+example,+Unicode::mimeHeaderEncode('tést.txt')+returns
+++*+"=?UTF-8?B?dMOpc3QudHh0?=".
+++*
+++*+See+http://www.rfc-editor.org/rfc/rfc2047.txt+for+more+information.
+++*
+++*+Notes:
+++*+-+Only+encode+strings+that+contain+non-ASCII+characters.
+++*+-+We+progressively+cut-off+a+chunk+with+self::truncateBytes().+This+ensures
+++*+++each+chunk+starts+and+ends+on+a+character+boundary.
+++*+-+Using+\n+as+the+chunk+separator+may+cause+problems+on+some+systems+and
+++*+++may+have+to+be+changed+to+\r\n+or+\r.
+++*
+++*+@param+string+$string
+++*+++The+header+to+encode.
+++*+@param+bool+$shorten
+++*+++If+TRUE,+only+return+the+first+chunk+of+a+multi-chunk+encoded+string.
+++*
+++*+@return+string
+++*+++The+mime-encoded+header.
+++*/
++public+static+function+mimeHeaderEncode($string,+$shorten+=+FALSE)+{
++++if+(preg_match('/[%5E\x20-\x7E]/',+$string))+{
++++++//+floor((75+-+strlen("=?UTF-8?B??="))+*+0.75);
++++++$chunk_size+=+47;
++++++$len+=+strlen($string);
++++++$output+=+'';
++++++while+($len+>+0)+{
++++++++$chunk+=+static::truncateBytes($string,+$chunk_size);
++++++++$output+.=+'+=?UTF-8?B?'+.+base64_encode($chunk)+.+"?=\n";
++++++++if+($shorten)+{
++++++++++break;
++++++++}
++++++++$c+=+strlen($chunk);
++++++++$string+=+substr($string,+$c);
++++++++$len+-=+$c;
++++++}
++++++return+trim($output);
++++}
++++return+$string;
++}|137051|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

The method mimeHeaderEncode($string) from the library class Unicode does the job.
<pre><code>$file_name= Unicode::mimeHeaderEncode($file_name);
</code></pre>
Example in drupal/php:
<pre><code>https://github.com/drupal/core-utility/blob/8.8.x/Unicode.php

/**
 * Encodes MIME/HTTP headers that contain incorrectly encoded characters.
 *
 * For example, Unicode::mimeHeaderEncode('tést.txt') returns
 * &quot;=?UTF-8?B?dMOpc3QudHh0?=&quot;.
 *
 * See http://www.rfc-editor.org/rfc/rfc2047.txt for more information.
 *
 * Notes:
 * - Only encode strings that contain non-ASCII characters.
 * - We progressively cut-off a chunk with self::truncateBytes(). This ensures
 * each chunk starts and ends on a character boundary.
 * - Using \n as the chunk separator may cause problems on some systems and
 * may have to be changed to \r\n or \r.
 *
 * @param string $string
 * The header to encode.
 * @param bool $shorten
 * If TRUE, only return the first chunk of a multi-chunk encoded string.
 *
 * @return string
 * The mime-encoded header.
 */
 public static function mimeHeaderEncode($string, $shorten = FALSE) {
 if (preg_match('/[^\x20-\x7E]/', $string)) {
 // floor((75 - strlen(&quot;=?UTF-8?B??=&quot;)) * 0.75);
 $chunk_size = 47;
 $len = strlen($string);
 $output = '';
 while ($len &gt; 0) {
 $chunk = static::truncateBytes($string, $chunk_size);
 $output .= ' =?UTF-8?B?' . base64_encode($chunk) . &quot;?=\n&quot;;
 if ($shorten) {
 break;
 }
 $c = strlen($chunk);
 $string = substr($string, $c);
 $len -= $c;
 }
 return trim($output);
 }
 return $string;
 }
</code></pre>

Web applications that want to force a resource to be downloaded rather than directly rendered in a Web browser issue a <code>Content-Disposition</code> header in the HTTP response of the form:
<code>Content-Disposition: attachment; filename=FILENAME</code>
The <code>filename</code> parameter can be used to suggest a name for the file into which the resource is downloaded by the browser. <a href="https://www.rfc-editor.org/rfc/rfc2183" rel="noreferrer">RFC 2183</a> (Content-Disposition), however, states in <a href="https://www.rfc-editor.org/rfc/rfc2183#section-2.3" rel="noreferrer">section 2.3</a> (The Filename Parameter) that the file name can only use US-ASCII characters:
<blockquote>
Current [RFC 2045] grammar restricts
parameter values (and hence
Content-Disposition filenames) to
US-ASCII. We recognize the great
desirability of allowing arbitrary
character sets in filenames, but it is
beyond the scope of this document to
define the necessary mechanisms.
</blockquote>
There is empirical evidence, nevertheless, that most popular Web browsers today seem to permit non-US-ASCII characters yet (for the lack of a standard) disagree on the encoding scheme and character set specification of the file name. Question is then, what are the various schemes and encodings employed by the popular browsers if the file name “naïvefile” (without quotes and where the third letter is U+00EF) needed to be encoded into the Content-Disposition header?
For the purpose of this question, popular browsers being:
<ul>
<li>Google Chrome</li>
<li>Safari</li>
<li>Internet Explorer or Edge</li>
<li>Firefox</li>
<li>Opera</li>
</ul>

How to encode the filename parameter of Content-Disposition header in HTTP?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

希望强制下载资源而不是直接在Web浏览器中呈现的Web应用程序在表单的HTTP响应中发出Content-Disposition标题：Content-Disposition: attachment; filename=FILENAMEfilename参数可用于建议浏览器下载资源的文件的名称。但是， (内容处理)在 (文件...

问如何在HTTP中编码内容配置标头的文件名参数？
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在HTTP中编码内容配置标头的文件名参数？EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在HTTP中编码内容配置标头的文件名参数？
EN