搜索 | 用户支持

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

详细了解

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: