Content-Disposition with a '%20' in the filename and without a extension not getting decoded

Duplicate Issue #11779112 • See Issue #11779136


Karuppiah S.
Apr 25, 2017
This issue is public.
See progress on Bug #11779136
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

In our application we are using file download. And in one of the case we are not giving the file extension and only the file name is being given.

And the filename will be having the spaces. Before it gets assigned to the Content-Disposition response header we are encoding those spaces by ‘%20’ as per the recommended ‘UTF-8’ encoding.

Eg: Content-Disposition attachment; filename="Additional%20material%20received%20from%20Correspondent"

The downloaded file also having the file name with ‘%20’ and not spaces.

But the same thing is working fine if we have the extension.

Eg: Content-Disposition attachment; filename="Additional%20material%20received%20from%20Correspondent1.msg"

This is working fine in other browsers. Kindly review the issue and fix it in IE.



0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “James M.”

      Changed Status to “Duplicate”

    • Hello,

      Thank you for providing this information about the issue. We are currently tracking this problem in case 11779136 and will continue to update you there.

      Best Wishes,

      The MS Edge Team

    • This bug has marked as duplicate. Please follow the parent issue to get new updates.

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

    Sign in