09-01-2017, 01:34 PM
Ralphy <== Blame this guy!
The --no-proxy statement should be removed, but a timeout should be there anyways (maybe a little higher) since that prevents anomalies like hanging reads and infinite connects. High latency shouldn't necessary be a problem with the current 2 attempts. We went as far as testing with dnscrypt-proxy and no cache to ensure that we could get the timeout as low as possible without failures. If there are DNS queries taking over 1000ms in a network, maybe that's what should be addressed in the first place.
It was left there unintentionally (like I said, blame that guy)... I was testing the new widget updates and didn't want to get a cached version from the local proxy; that's how it got there
![Smile Smile](https://www.freecinema2022.gq/forums/images/smilies/smile.png)
https://unlockforus.com
Sorry for seeming stupid and preferring Linux - I just don't know any better.
Sorry for seeming stupid and preferring Linux - I just don't know any better.
![[Image: AGxgqJ6.png]](http://i.imgur.com/AGxgqJ6.png)