[drop] plugin HTTPS rewrite - rule base is to old (update is to big)

The usefulness of the _HTTPS rewrite_ plugin is questionable:

- the 36 rule files have not been updated since 2015 [1]
- actual there are 23760 rule files in the https-everywhere repo [2]

For the first, we can remove this plugin.  For a complete new implementation, it
might be good to know that there is a project "https-everywhere : Privacy for
Pythons" [3]

related:  https://github.com/return42/searx-next/issues/8

[1] https://github.com/return42/searx-next/tree/d187a1d/searx/plugins/https_rules
[2] https://github.com/EFForg/https-everywhere/tree/master/src/chrome/content/rules
[3] https://github.com/jayvdb/https-everywhere-py

Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>

1 files changed, 0 insertions, 17 deletions

diff --git a/searx/plugins/https_rules/00README b/searx/plugins/https_rules/00README
deleted file mode 100644
index fcd8a7724..000000000
--- a/searx/plugins/https_rules/00README
+++ /dev/null
@@ -1,17 +0,0 @@
-<!-- 
-This directory contains web site rewriting rules for the
-HTTPS Everywhere software, available from
-https://www.eff.org/https-everywhere
-
-These rules were contributed to the project by users and aim to
-enable routine secure access to as many different web sites as
-possible.  They are automatically installed together with the
-HTTPS Everywhere software.  The presence of these rules does not
-mean that an HTTPS Everywhere user accessed, or intended to
-access, any particular web site.
-
-For information about how to create additional HTTPS Everywhere
-rewriting rules to add support for new sites, please see
-
-https://www.eff.org/https-everywhere/rulesets
--->