0
Started

Content-Disposition header field (RFC 6266)

irabu 8 months ago updated 7 months ago 2

Dear Sirs,

I checked "Content-Disposition" header when I downloaded by IE.


Present, I think that "Content-Disposition" is written as:

    header('Content-Disposition: attachment; filename=' . [FILENAME]);

In this case the file that named by non-ascii characters will be broken with IE or Edge.

Can you change that header as below?:

   header('Content-Disposition: attachment; filename*=UTF-8\'\'' . rawurlencode([FILENAME]);


Please check RFC6266.

Thank you

Started

I wish it was that simple. Edge still does not respect the standards, so "filename*" (with a star) doesn't do anything. Not even Chrome is handling that particular header part. A workaround was added for Internet Explorer, so that should still work, but even if it doesn't we do not care as we have dropped support for it.

We'll add the workaround for Edge in the next update.

Thanks for your answer, Vlad,

I want that IE will be disappear.;P

There is no hurry.
I have way to replace headers at proxy server.


Thank you