You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 7, 2023. It is now read-only.
Is your feature request related to a problem? Please describe.
When searching from Google through searx, Google sometimes decides it's too many requests or if it determines that they're suspicious or robot-looking, it can display a CAPTHCA, which makes searx unable to return results.
A single user can trigger a CAPTCHA, I know since I have gotten a CAPTCHA on my normal IP address by typing queries that include parameters like site: on my keyboard.
Describe the solution you'd like
Since searx users are humans, searx could forward the CAPTCHA to them in order to complete the search. I wouldn't mind being asked to tell searx which of the pictures are cars, so it can reply that to Google.
Describe alternatives you've considered
From searching open issues, #2439 proposes falling back to another proxy, but these may be limited -- what if all of the proxies display a CAPTCHA? Many instances may have only one IP address available, which may trigger the CAPTCHA.
Additional context
None
The text was updated successfully, but these errors were encountered:
@unixfox while it may not be possible to display this with web technologies, I can think of ways to do it:
Screen mirroring a browser instance (something like VNC)
Also using a browser instance on the server: Parse the contents of the CAPTCHA itself, and show them to the user so the user can click on the image of a car or whatever the CAPTCHA asks for. Then the server returns to the CAPTCHA what the user selected.
Is your feature request related to a problem? Please describe.
When searching from Google through searx, Google sometimes decides it's too many requests or if it determines that they're suspicious or robot-looking, it can display a CAPTHCA, which makes searx unable to return results.
A single user can trigger a CAPTCHA, I know since I have gotten a CAPTCHA on my normal IP address by typing queries that include parameters like
site:
on my keyboard.Describe the solution you'd like
Since searx users are humans, searx could forward the CAPTCHA to them in order to complete the search. I wouldn't mind being asked to tell searx which of the pictures are cars, so it can reply that to Google.
Describe alternatives you've considered
From searching open issues, #2439 proposes falling back to another proxy, but these may be limited -- what if all of the proxies display a CAPTCHA? Many instances may have only one IP address available, which may trigger the CAPTCHA.
Additional context
None
The text was updated successfully, but these errors were encountered: