Edge doesn't ignore LWSP when parsing RFC5987 encoded filenames in "content-disposition" response header

Issue #16185868 • Assigned to Divya G.

Details

Author
Christof L.
Created
Mar 2, 2018
Privacy
This issue is public.
Found in
  • Microsoft Edge
  • Internet Explorer
Found in build #
16.16299
Reports
Reported by 2 people

Sign in to watch or report this issue.

Steps to reproduce

Outdated repro

When I open the following URL in Edge it shows a “Save as” dialog with the wrong filename:

http://wuerth-test.k-infinity.com/wuerth-analyse/rest/test/test

I would expect that the filename returned in the “Content-Disposition” header (“Sanitär, Heizung, Klima.bmp”) would be recognized and displayed by Edge. The filename is correctly decoded in current Firefox and Chrome versions.

Attachments

0 attachments

    Comments and activity

    • Sorry, i´ve provided the wrong download URL. The correct URL is:

      https://wuerth-test.k-infinity.com/wuerth-analyse/rest/test/Sanitär,%20Heizung,%20Klima.bmp

    • Microsoft Edge Team

      Changed Assigned To to “Venkat K.”

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

    • I can confirm this issue - impacts any files downloaded from ServiceNow for example.

    • Is there a live repro url for this issue that is still online? I get a 404 for these URLs from both Edge and Chrome.

      IE9 introduced support 
      RFC5987 for UTF-8 filenames in the 
      filename*
      parameter, but it’s not clear whether that format is in use here.

    • Microsoft Edge Team

      Changed Steps to Reproduce

      Changed Title from “Edge doesn't decode UTF-8 Base64 encoded filenames in "content-disposition" reponse header” to “Edge doesn't decode RFC5987 encoded filenames in "content-disposition" response header”

      Changed Title from “Edge doesn't decode RFC5987 encoded filenames in "content-disposition" response header” to “Edge doesn't ignore LWSP when parsing RFC5987 encoded filenames in "content-disposition" response header”

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

    Sign in