How to confirm if limiter+redis is working? #1114
-
|
Is there a way to confirm if it's working as intended? I have setup my instance with limiter+redis and everything seems to be working fine. On the surface at least. I couldn't find a way to test if limiter is working or not though. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 7 replies
-
|
You can do a Curl request. The limiter currently is there to rate limited and protect searches. So for example this will be blocked by the limiter (since curl is a bot in its current impl.): You can change the domain to your instance and test it yourself. If you get something like this it works correctly: (Important is the HTTP 429 rate limit response) Does this answer your question? |
Beta Was this translation helpful? Give feedback.
-
Thanks. Changing |
Beta Was this translation helpful? Give feedback.
-
|
To elaborate on this: The |
Beta Was this translation helpful? Give feedback.
-
This should be added to the docs, right? Not adding |
Beta Was this translation helpful? Give feedback.
-
|
I'm getting "HTTP/1.1 429 TOO MANY REQUESTS" so Redis/Limiter plugin is working? |
Beta Was this translation helpful? Give feedback.
-
|
Yeah if you get a HTTP 429 response with curl than the limiter plugin in SearXNG with redis is working 👍 |
Beta Was this translation helpful? Give feedback.
You can do a Curl request. The limiter currently is there to rate limited and protect searches. So for example this will be blocked by the limiter (since curl is a bot in its current impl.):
You can change the domain to your instance and test it yourself. If you get something like this it works correctly: