4 ms·
There is a global timeout. If for some reason, all engines doesn't response before the global timeout, there is no result. Usually it's work on the second try
by dalf 9y ago
There is a global timeout. If for some reason, all engines doesn't response before the global timeout, there is no result.
Usually it's work on the second try because the HTTPS connection are already established (which may be not the case on the first try).
One idea to avoid the annoying refresh : if there is no result before the global timeout, searx could wait longer.
- jcalabro 9y agoAppreciate you raising the issue! I will be sure to follow it.
- jcalabro 9y agoAlso, maybe calling it a bug was a little unfair; if it is a timeout, it seems to be working as expected. We'll see. Either way, I really liked it while I was using it, hopefully it gets resolved! Good work SearX contributors! :)