Avatar for Username

Mozilla サポートの検索

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

詳しく学ぶ

このスレッドはアーカイブに保管されました。 必要であれば新たに質問してください。

Improper handling of RFC5987 HTTP parameters such as filename

  • 1 件の返信
  • 1 人がこの問題に困っています
  • 1 回表示
  • 最後の返信者: pfriend

pfriend
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)

pfriend
pfriend 質問者
more options

選ばれた解決策

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

この投稿は pfriend により に変更されました