diff options
| -rw-r--r-- | searx/engines/google.py | 4 | ||||
| -rw-r--r-- | searx/plugins/limiter.py | 2 | ||||
| -rwxr-xr-x | searx/webapp.py | 2 |
3 files changed, 5 insertions, 3 deletions
diff --git a/searx/engines/google.py b/searx/engines/google.py index e5f24b166..acc87307b 100644 --- a/searx/engines/google.py +++ b/searx/engines/google.py @@ -13,9 +13,9 @@ The google WEB engine itself has a special setup option: - name: google ... - use_mobile_ui: true + use_mobile_ui: false -``use_mobile_ui``: (default: ``true``) +``use_mobile_ui``: (default: ``false``) Enables to use *mobile endpoint* to bypass the google blocking (see :issue:`159`). On the mobile UI of Google Search, the button :guilabel:`More results` is not affected by Google rate limiting and we can still do requests diff --git a/searx/plugins/limiter.py b/searx/plugins/limiter.py index c3ec64283..4402900e8 100644 --- a/searx/plugins/limiter.py +++ b/searx/plugins/limiter.py @@ -3,7 +3,7 @@ # pyright: basic """Some bot protection / rate limitation -To monitore rate limits and protect privacy the IP addresses are getting stored +To monitor rate limits and protect privacy the IP addresses are getting stored with a hash so the limiter plugin knows who to block. A redis database is needed to store the hash values. diff --git a/searx/webapp.py b/searx/webapp.py index 2c633fbea..7eca07753 100755 --- a/searx/webapp.py +++ b/searx/webapp.py @@ -454,6 +454,8 @@ def render(template_name: str, **kwargs): # values from the preferences kwargs['preferences'] = request.preferences + kwargs['autocomplete'] = request.preferences.get_value('autocomplete') + kwargs['infinite_scroll'] = request.preferences.get_value('infinite_scroll') kwargs['results_on_new_tab'] = request.preferences.get_value('results_on_new_tab') kwargs['advanced_search'] = request.preferences.get_value('advanced_search') kwargs['query_in_title'] = request.preferences.get_value('query_in_title') |