Content-Disposition header filename encoding

Fixed Issue #8328173


Power U.
Jul 29, 2016
This issue is public.
Found in
  • Microsoft Edge
  • Internet Explorer
Fixed in build #
Reported by 3 people

Sign in to watch or report this issue.

Steps to reproduce

When the server sends a file for download using Content-Disposition HTTP header with a filename encoded according to and the encoded filename contains encoded space Edge and IE11 do not decode the space properly.

Using an example from

Content-Disposition: attachment; filename*= UTF-8''%e2%82%ac%20rates

IE11 and Edge show “Save As…” dialog with an incorrect file name “€%20rates” instead of "€ rates".


0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Ibrahim O.”

    • Thank you for your feedback. Could you please attach your repro page or the link that can demonstrate the issue. This will help our investigation.

      All the best,
      The MS Edge Team

    • Microsoft Edge Team

      Changed Assigned To to “Venkat K.”

      Changed Assigned To from “Venkat K.” to “Divya G.”

    • Hi , I had the similar issue but it got solved after encoding the file name as below.
      filename =,"UTF-8");

      Here spaces get replaced from + sign so I replaced them with spaces again
      filename = filename.replace("+", " ");

      With above two steps I could get the non ASCII characters working in Edge. Tested for Swedish and Japanese .

    • Microsoft Edge Team

      Changed Status to “Fixed”

    • Hello,

      Thank you for providing this information about the issue. We are pleased to report this feature is fixed in Edge 15063 and is available in our latest Insider Preview build.

      Best Wishes,
      The MS Edge Team

    You need to sign in to your Microsoft account to add a comment.

    Sign in