[fix] limiter.toml: botdetection.ip_limit turn off link_token by default

To activate the ``link_token`` method in the ``ip_limit`` method add the
following to your ``/etc/searxng/limiter.toml``::

   [botdetection.ip_limit]
   link_token = true

Related: https://github.com/searxng/searxng/pull/2357#issuecomment-1554116941
Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
This commit is contained in:
Markus Heiser 2023-05-27 18:58:06 +02:00
parent 66fdec0eb9
commit 9d7456fd6c
2 changed files with 13 additions and 4 deletions

View file

@ -9,9 +9,18 @@ bot request. This method requires a redis DB and needs a HTTP X-Forwarded-For_
header. To take privacy only the hash value of an IP is stored in the redis DB header. To take privacy only the hash value of an IP is stored in the redis DB
and at least for a maximum of 10 minutes. and at least for a maximum of 10 minutes.
The :py:obj:`link_token` method is used to investigate whether a request is The :py:obj:`.link_token` method can be used to investigate whether a request is
*suspicious*. If the :py:obj:`link_token` method is activated and a request is *suspicious*. To activate the :py:obj:`.link_token` method in the
*suspicious* the request rates are reduced: :py:obj:`.ip_limit` method add the following to your
``/etc/searxng/limiter.toml``:
.. code:: toml
[botdetection.ip_limit]
link_token = true
If the :py:obj:`.link_token` method is activated and a request is *suspicious*
the request rates are reduced:
- :py:obj:`BURST_MAX` -> :py:obj:`BURST_MAX_SUSPICIOUS` - :py:obj:`BURST_MAX` -> :py:obj:`BURST_MAX_SUSPICIOUS`
- :py:obj:`LONG_MAX` -> :py:obj:`LONG_MAX_SUSPICIOUS` - :py:obj:`LONG_MAX` -> :py:obj:`LONG_MAX_SUSPICIOUS`

View file

@ -1,3 +1,3 @@
[botdetection.ip_limit] [botdetection.ip_limit]
link_token = true link_token = false