Skip to content
This repository has been archived by the owner on Sep 7, 2023. It is now read-only.

Extend global timeout when there is no result #948

Open
dalf opened this issue Jun 19, 2017 · 0 comments
Open

Extend global timeout when there is no result #948

dalf opened this issue Jun 19, 2017 · 0 comments
Labels

Comments

@dalf
Copy link
Contributor

dalf commented Jun 19, 2017

Currently, if all search engines timeout, the user doesn't have any result to read.
In this scenario, the user usually refresh the page to make sure there is really no result : and sometimes it displays some results.

Technically, this can happen when the HTTPS connections have been closed. On the second try, the connections are already opened, and the results arrived before the global timeout.

See : https://news.ycombinator.com/item?id=14579491#14581065

I see two solutions (most probably there are a lot of more) :

  • advise the administrator to increase the global timeout in this case. How ?
  • change the searx behavior : if there is no results after the timeout, double the timeout and wait more.
@dalf dalf added the ui / ux label Jun 19, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant