搜尋 Mozilla 技術支援網站

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

了解更多

icloud mail attachments are corrupt if they contain spaces and downloaded via firefox

  • 1 回覆
  • 9 有這個問題
  • 4 次檢視
  • 最近回覆由 cor-el

more options

If you are accessing mail in icloud via firefox any attachment which contains spaces when saved will be corrupt. E.g "invoice for previous month.doc" when saved will come out as "invoice" with no file type and not the orginal size of the attachment. This problem is generic for all file types. Files that do not contain spaces or have _ in them download and save correctly.

I have tested this using the latest versions of firefox also default settings. On both windows 7 and OS X lion. The problem still exists. I have had friends with other accounts test this and all with the same result. I have spoken to apple care who isolated the problem and requested that the issue be taken to firefox directly. The problem has been ongoing for a year or so.

All other browsers have no issues with this problem.

If you have any idea on how to fix this your input would be greatly valued.

If you are accessing mail in '''icloud''' via '''firefox''' any attachment which ''contains spaces'' when saved will be corrupt. E.g "invoice for previous month.doc" when saved will come out as "invoice" with no file type and not the orginal size of the attachment. This problem is generic for all file types. Files that do not contain spaces or have _ in them download and save correctly. I have tested this using the latest versions of firefox also default settings. On both windows 7 and OS X lion. The problem still exists. I have had friends with other accounts test this and all with the same result. I have spoken to apple care who isolated the problem and requested that the issue be taken to firefox directly. The problem has been ongoing for a year or so. All other browsers have no issues with this problem. If you have any idea on how to fix this your input would be greatly valued.

所有回覆 (1)

more options

Sounds that the server doesn't comply to RFC 5987 and sends the wrong Content-Disposition:attachment; filename header.

See the 3.2.2. Examples section: