为提升您的使用体验,本站正在维护,部分功能暂时无法使用。如果本站文章无法解决您的问题,您想要向社区提问的话,请到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 提问,我们的支持社区将会很快回复您的疑问。

搜索 | 用户支持

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

详细了解

Use data-sha1 attribute to compare scripts, css, etc. avoiding the need for CDNs that track

  • 2 个回答
  • 1 人有此问题
  • 3 次查看
  • 最后回复者为 AliceWonder

more options

Hi, I would like to see an attribute added to FireFox (and every browser) to decrease tracking.

When webmasters use a public CDN (e.g. scripts.google.com or wherever) for things like jQuery etc., they are potentially opening up their users to tracking by those CDNs.

If we had a data-sha1 attribute that could contain the sha1sum of the script we are referencing, it could improve security and privacy in two ways:

A) Prevent cases where the CDN has been compromised altering the resource being referenced, because then the checksum won't match.

B) If the browser already has a script cached with a matching checksum, then it doesn't need to fetch it from any CDN or server etc. or even ask if the version it has is current. If the checksum of a resource in cache matches, then it is the same file regardless of where it came from and the browser does not need to send any headers to anyone.

Okay, the possibility of collisions exist even though the odds are astronomically low, so maybe verify the filename matches too.

Hi, I would like to see an attribute added to FireFox (and every browser) to decrease tracking. When webmasters use a public CDN (e.g. scripts.google.com or wherever) for things like jQuery etc., they are potentially opening up their users to tracking by those CDNs. If we had a data-sha1 attribute that could contain the sha1sum of the script we are referencing, it could improve security and privacy in two ways: A) Prevent cases where the CDN has been compromised altering the resource being referenced, because then the checksum won't match. B) If the browser already has a script cached with a matching checksum, then it doesn't need to fetch it from any CDN or server etc. or even ask if the version it has is current. If the checksum of a resource in cache matches, then it is the same file regardless of where it came from and the browser does not need to send any headers to anyone. Okay, the possibility of collisions exist even though the odds are astronomically low, so maybe verify the filename matches too.

所有回复 (2)

more options

Suggestions to improve Firefox can be submitted here: https://input.mozilla.org/en-US/feedback

Or a Bug report can be filed. https://bugzilla.mozilla.org/

https://developer.mozilla.org/en/Bug_writing_guidelines

more options

Their feedback seems to be about existing features as the interface wants to know what made me happy or sad, and this is a request - not feedback on what made me happy or sad.

It's also not a bug.