In my asp.net mvc application I have the code: response.ContentType = application/octet-stream; response.AddHeader(Content-Disposition, attachment;filename=

Question

0

Asked: May 25, 20262026-05-25T09:31:27+00:00 2026-05-25T09:31:27+00:00

In my asp.net mvc application I have the code: response.ContentType = application/octet-stream; response.AddHeader(Content-Disposition, attachment;filename=

0

In my asp.net mvc application I have the code:

response.ContentType = "application/octet-stream";
response.AddHeader("Content-Disposition", "attachment;filename=" + 
    HttpUtility.UrlEncode(attachment.FileName));

So that all the Chinese characters are url-encoded to something like %5C%2D. In IE/Chrome when users download the file, they get the Chinese file name(that is, IE/Chrome will automatically url-decode the file name). But in Firefox, they will get something like %5C%2D%0A.docx. Now I’m going to remove HttpUtility.UrlEncode in the code. But before doing this, I want to confirm that there is no security issues in this case. Would you please give me some ideas?

EDIT Corbin’s answer is correct. But after removing the url-encoding of the filename, some users using old version IE will get strange messy file names. At last I do url-encode for those users only.