Https-everywhere: Add some hosters/domain registrars

[rugk]

• [x] https://www.domaindiscount24.com
• [x] https://rage4.com/
• [x] https://www.royaldns.net/
• [x] https://www.transip.de/
• [x] https://www.rb-media-group.de/
• [ ] https://www.rrpproxy.net/
• [ ] https://www.omc.net/
• [ ] https://www.mk.de/
• [ ] https://www.mcs.de/
• [ ] https://joker.com/
• [ ] https://www.internetx.com
• [ ] https://www.epag.de/
• [ ] https://www.edns.de/
• [ ] https://domainexpress.de/
• [x] https://desec.io
• [x] https://www.dotplex.de/
• [x] https://www.cps-datensysteme.de
• [x] https://www.core-networks.de/
• [x] https://www.123domain.eu/

[J0WI]

It would be great to get a pull request from you!
https://github.com/EFForg/https-everywhere/blob/master/ruleset-style.md

[rugk]

If I get time I will do.

[rugk]

dotplex.de already has a rule: https://github.com/EFForg/https-everywhere/blob/fe756cd650cdc4b81a25b93982fe86be801037f6/src/chrome/content/rules/Dotplex.de.xml

[zneaa]

@rugk joker.com.xml https://github.com/EFForg/https-everywhere/pull/8891

[zneaa]

@rugk cps-datensysteme.de.xml https://github.com/EFForg/https-everywhere/issues/2324

[zneaa]

@rugk core-networks.de.xml https://github.com/EFForg/https-everywhere/issues/8893

[jeremyn]

I've closed pull request https://github.com/EFForg/https-everywhere/pull/8892 without merging it, so cps-datensysteme.de still needs a ruleset.

[RemakingEden]

@J0WI I'm slightly confused on some of these older issues. I'm new to contributing so i'm sorry if this is a basic question. Ive just tested a lot of these and they all seem to resolve to https automatically.

Should I check all of them and if they all resolve automatically should this be closed? Or if thye resolve automatically, is it still good to make rulesets for them?

Thanks for the help!

[rugk]

@RemakingEden It does not matter if a site automatically redirects to HTTPS. See https://www.eff.org/https-everywhere/faq#why-does-https-everywhere-include-rules-for-sites-like-paypal-that-already-require-https-on-all-their-pages

[RemakingEden]

@rugk thanks for the info! So does this mean we should make rulesets for every single website out there? It seems like the extension may get impossibly large then?

[J0WI]

Yes, our goal is to have HTTPS Everywhere and the infinitely growing database is an issue we can't really solve as long as unsecured connections are still supported.
We remove rulesets for domains that support preloaded HSTS, but this is also a infinitely growing database in browsers. Some new TLD are preloaded itself, so things will be easier there.

[RemakingEden]

@rugk Added new rulesets for Rrpproxy and Rb-media-group https://github.com/EFForg/https-everywhere/pull/17370 https://github.com/EFForg/https-everywhere/pull/17369

[pipboy96]

See #17760, #17759, #17758, #17757, #17756, #17755, #17754, #17753, #17752.