Actions
Bug #1221
closed
JG
SS
HTTP 429 response on SearxNG searches
Bug #1221:
HTTP 429 response on SearxNG searches
Start date:
09/15/2024
Due date:
% Done:
0%
Estimated time:
Description
When trying to search for anything on SearXNG instances, the server returns an HTTP 429 response and the text “Too Many Requests”.
Looking at their code (https://github.com/searxng/searxng/tree/master/searx/botdetection), the reason seems to be that Privacy Browser PC doesn't send certain headers that SearXNG expects in order to distinguish between a bot and a legitimate user. The headers in question are:
- Accept-Encoding: any string containing ‘gzip’, ‘deflate’ or both will do, but of course a spec-wise correct value would be much better.
- Accept-Language: its mere presence will do. I tested it using ‘*’ and it worked.
- Connection: it must be sent in the request and its value MUST NOT be ‘close’. (I tested it with ‘keep-alive’ personally.)
There's another header that's checked (‘User-Agent’), but here Privacy Browser PC complies.
Incidentally, this doesn't happen with the Android version.
Files
Actions