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
httpsWhitelist.js fetches open issues and pull requests from https://api.github.com/repos/EFForg/https-everywhere/issues to build a https upgrade whitelist. As closed issues/pull requests are not fetched and the https-everywhere ruleset seems not to be included, a domain could be upgraded to https even if an exclusion exists in the https-everyhwere ruleset.
How is the DDG content-blocking https list generated (and can a pull request be stated to restore functionality for the example domain)?
Is it possible to include the https-everywhere ruleset for exclusion-pattern handling?
The text was updated successfully, but these errors were encountered:
httpsWhitelist.js fetches open issues and pull requests from https://api.github.com/repos/EFForg/https-everywhere/issues to build a https upgrade whitelist. As closed issues/pull requests are not fetched and the https-everywhere ruleset seems not to be included, a domain could be upgraded to https even if an exclusion exists in the https-everyhwere ruleset.
Example domain: breitbandmessung.de
Closed Ruleset Issue: #9841
Ruleset excludes the URIs /test, /images, /api, /public from https upgrade
DDG content-blocking https list includes the example domain: https://duckduckgo.com/contentblocking.js?l=https2
How is the DDG content-blocking https list generated (and can a pull request be stated to restore functionality for the example domain)?
Is it possible to include the https-everywhere ruleset for exclusion-pattern handling?
The text was updated successfully, but these errors were encountered: