搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

Learn More

Improper handling of RFC5987 HTTP parameters such as filename

  • 1 个回答
  • 1 人有此问题
  • 1 次查看
  • 最后回复者为 pfriend

more options

I have files on my website whose names are in UTF-8 and contain characters outside the ASCII set. I am setting the Content-Disposition header as an attachment with a filename* parameter encoded per RFC5987. The non-ascii characters are translated fine, but there appears to be a problem handling space encoding (%20). Per this RFC spaces in the filename are encoded as %20, but when I download the file these encoded space characters are being converted to + characters which is incorrect. This appears to be a bug in Firefox (Chrome as well I might add).

I have files on my website whose names are in UTF-8 and contain characters outside the ASCII set. I am setting the Content-Disposition header as an attachment with a filename* parameter encoded per RFC5987. The non-ascii characters are translated fine, but there appears to be a problem handling space encoding (%20). Per this RFC spaces in the filename are encoded as %20, but when I download the file these encoded space characters are being converted to + characters which is incorrect. This appears to be a bug in Firefox (Chrome as well I might add).

被采纳的解决方案

Ignore this one. Turns out there was a unicode conversion bug that was causing this, Firefox is all good. :-)

定位到答案原位置 👍 0

所有回复 (1)

more options

选择的解决方案

Ignore this one. Turns out there was a unicode conversion bug that was causing this, Firefox is all good. :-)

由pfriend于修改