Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

httpsWhitelist.js fetches only open issues from https-everywhere #132

Open
kosekmi opened this issue Feb 13, 2018 · 0 comments
Open

httpsWhitelist.js fetches only open issues from https-everywhere #132

kosekmi opened this issue Feb 13, 2018 · 0 comments
Assignees
Labels
needs response issue that needs a response from the product team

Comments

@kosekmi
Copy link

kosekmi commented Feb 13, 2018

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?

@alohaas alohaas added the needs response issue that needs a response from the product team label Mar 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs response issue that needs a response from the product team
Projects
None yet
Development

No branches or pull requests

3 participants