[GH-ISSUE #1011] [FEATURE] Auto-refresh if using proxy and instance is ratelimited #625

New issue

Closed

opened 2026-02-25 20:36:10 +03:00 by kerem · 0 comments

kerem commented

2026-02-25 20:36:10 +03:00

Owner

Originally created by @guneydoganer on GitHub (May 29, 2023).
Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/1011

Current situation:
Whether you're making use of a proxy service or not, once you're ratelimited, you get shown a page saying that the instance is ratelimited. You're also given a few options to use a different whoogle or searx instance.

I'm not that familiar with proxy services, but the one that I'm using at least has the option that for every request a new IP is used. Meaning that if I get ratelimited on my instance and do an autorefresh, I get the search results I want with a different proxy IP address.

I'm thinking of sharing my instance with the public, but it would go a long way in usability/user friendliness, if the enduser would just be able to search, without getting a ratelimit error, with a new proxy IP.

My proposal:
Give Whoogle administrators an additional option in the configuration settings (could be answered with a boolean) that would allow them to enable autorefresh on the ratelimit error page. If answered true, it'd enable/uncomment a small section on the ratelimit page that'd renew (refresh) the page in the browser.

For regular/local users of Whoogle this would probably be not interesting, but for those who use proxy services with renewing IP addresses, this could make quite a positive difference.

Considering this is not a big feature request nor a pressing matter, I think it would be easy to implement if the developer(s) have the time for it. Though IMO it shouldn't be prioritized over other feature requests/bugs and be considered a "nice-to-have"feature request.

EIther way, thank you for all of the hard work!

Originally created by @guneydoganer on GitHub (May 29, 2023). Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/1011 **Current situation:** Whether you're making use of a proxy service or not, once you're ratelimited, you get shown a page saying that the instance is ratelimited. You're also given a few options to use a different whoogle or searx instance. I'm not that familiar with proxy services, but the one that I'm using at least has the option that for every request a new IP is used. Meaning that if I get ratelimited on my instance and do an autorefresh, I get the search results I want with a different proxy IP address. I'm thinking of sharing my instance with the public, but it would go a long way in usability/user friendliness, if the enduser would just be able to search, without getting a ratelimit error, with a new proxy IP. **My proposal:** Give Whoogle administrators an additional option in the configuration settings (could be answered with a boolean) that would allow them to enable autorefresh on the ratelimit error page. If answered true, it'd enable/uncomment a small section on the ratelimit page that'd renew (refresh) the page in the browser. For regular/local users of Whoogle this would probably be not interesting, but for those who use proxy services with renewing IP addresses, this could make quite a positive difference. Considering this is not a big feature request nor a pressing matter, I think it would be easy to implement if the developer(s) have the time for it. Though IMO it shouldn't be prioritized over other feature requests/bugs and be considered a "nice-to-have"feature request. EIther way, thank you for all of the hard work!