搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

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 於 修改