搜索 | 用户支持

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

Learn More

Downloaded files from internal site mark safe (Bug 909022)

more options

When opening word documents downloaded from our internal site, Word is now having us click enable editing to modify them. This didnt happen prior to FF 29. I found the following article saying how they were changing the behavior https://bugzilla.mozilla.org/show_bug.cgi?id=909022 . Is there a way to say any files downloaded from internal.domain.com are safe and dont mark them as coming from the internet?

THANKS

When opening word documents downloaded from our internal site, Word is now having us click enable editing to modify them. This didnt happen prior to FF 29. I found the following article saying how they were changing the behavior https://bugzilla.mozilla.org/show_bug.cgi?id=909022 . Is there a way to say any files downloaded from internal.domain.com are safe and dont mark them as coming from the internet? THANKS

所有回复 (3)

more options

It doesn't work as described in the bug report you linked. Things must've changed some time between Firefox 26 and Firefox 29. The about:config preference mentioned at comment 11 doesn't work; configuring the setting in the Group Policy Editor does work.

  1. Press the Windows logo orb on the taskbar to bring up the Start Menu.
  2. In the search box, type gpedit.msc
  3. In the search results, right-click gpedit.msc and choose Run As Administrator.
  4. On the left, expand the User Configuration section, then Administrative Templates, then Windows Components, and lastly Attachment Manager.
  5. On the right, double-click "Do not preserve zone information in file attachments"
  6. In the window that opens, click Enabled, then OK. Firefox must be restarted for the change to take effect.
more options

Gingerbread,

Thanks for the reply. Unfortunately that will make the change across all browsers. I just want this to affect FF

more options

hogster wrote:

I just want this to affect FF

That's no longer possible. It's been brought up before the release of Firefox 29. See how the conversation went:

Please read the Bugzilla etiquette page before deciding to comment on bug reports.

If you need this in an enterprise environment, it's best to discuss the issue on the Enterprise Working Group mailing list. You're not going to get the appropriate attention on this user support forum.