HTTP GET timeout is so big: we should provide a shorter timeout for not working connections
Trying to add a new provider with a main url which is not correct and which does not respond quickly to our GET request (https://as.com, I used), I was hooked up by the HTTP timeout during a lot of seconds.
We should avoid this situations because the user would get desperate because of his own error, feeling angry with the app.
(from redmine: created on 2013-04-16, closed on 2013-12-09)
- Relations:
- relates #2225 (closed)