You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Note: this can be done by anyone, given that our FAQ is generated from a template in #13762 (comment). I'll just need to be pinged to actually update the eff.org FAQ based on this template.
Please note that I am not a native speaker but here are some
webRequestBlocking: The permission to block requests is required for blocking HTTP requests in HTTPS only mode. A single HTTP request can leak information about your browsing history to an eavesdropper. An example is the referrer header which includes the URL from the website from which the request originated. Browsers like Firefox do not allow active content like scripts to be loaded via HTTP on a HTTPS site (only images etc.) but it is still possible to manipulate this content.
cookies: Cookies (small data chunks sent with each request) supports a flag to send them only over TLS connections. Cookies are used for managing sessions on top of stateless HTTP to allow things like logging into a website, store preferences or tracking. This permission is required to set the flag to sent cookies only via TLS if the server does not set it by itself.
Activity
Hainish commentedon Dec 1, 2017
Note: this can be done by anyone, given that our FAQ is generated from a template in #13762 (comment). I'll just need to be pinged to actually update the eff.org FAQ based on this template.
fabianfrz commentedon Dec 7, 2017
Please note that I am not a native speaker but here are some
webRequestBlocking: The permission to block requests is required for blocking HTTP requests in HTTPS only mode. A single HTTP request can leak information about your browsing history to an eavesdropper. An example is the referrer header which includes the URL from the website from which the request originated. Browsers like Firefox do not allow active content like scripts to be loaded via HTTP on a HTTPS site (only images etc.) but it is still possible to manipulate this content.
cookies: Cookies (small data chunks sent with each request) supports a flag to send them only over TLS connections. Cookies are used for managing sessions on top of stateless HTTP to allow things like logging into a website, store preferences or tracking. This permission is required to set the flag to sent cookies only via TLS if the server does not set it by itself.
zoracon commentedon Jul 23, 2020
This has been addressed here: https://www.eff.org/https-everywhere/faq#https-everywhere-asking-for-my-website-data