[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, 16 deletions

diff --git a/searx/plugins/https_rules/Googleplex.com.xml b/searx/plugins/https_rules/Googleplex.com.xml
deleted file mode 100644
index 7ddbb5ba9..000000000
--- a/searx/plugins/https_rules/Googleplex.com.xml
+++ /dev/null
@@ -1,16 +0,0 @@
-<!-- This rule was automatically generated based on an HSTS
-     preload rule in the Chromium browser.  See 
-     https://src.chromium.org/viewvc/chrome/trunk/src/net/base/transport_security_state.cc
-     for the list of preloads.  Sites are added to the Chromium HSTS
-     preload list on request from their administrators, so HTTPS should
-     work properly everywhere on this site.
- 
-     Because Chromium and derived browsers automatically force HTTPS for
-     every access to this site, this rule applies only to Firefox. -->
-<ruleset name="Googleplex.com (default off)" platform="firefox" default_off="Certificate error">
-  <target host="googleplex.com" />
-
-  <securecookie host="^googleplex\.com$" name=".+" />
-
-  <rule from="^http://googleplex\.com/" to="https://googleplex.com/" />
-</ruleset>