search

githubashto / slimrat

Automatically exported from code.google.com/p/slimrat
MIT License
0 stars 0 forks source link

Fail proxy removal #76

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What feature are you missing?
Can you implement when using proxy, to remove proxy server from list if 
download fail ?

Original issue reported on code.google.com by petar.bojovic.paxy@gmail.com on 7 Sep 2009 at 8:14

GoogleCodeExporter commented 9 years ago 
What is the error slimrat reports when failing a download due to a proxy
timeout/error? Is it a regular 505 gateway timeout, or something other? I want 
to be
able to detect whether the proxy timed out. If impossible, I'd rather build in 
some
check (e.g. load google) at proxy load.
TBH, I don't really know how to tackle this, and I don't want to kick out a 
proxy
without knowing if it actually is defunct.

Original comment by tim.besard@gmail.com on 7 Sep 2009 at 10:53

GoogleCodeExporter commented 9 years ago 
I have seen two error for now.
One is soft error like RapidShare is unreachable, retrying (I enabled retrying).
Other one is can not find ff form when try to download file. 

In both cases, thread detect error and do skip or retry action.
You can just add part that would delete this IP from proxy list and try with 
next one.

Original comment by petar.bojovic.paxy@gmail.com on 7 Sep 2009 at 11:25

GoogleCodeExporter commented 9 years ago 
Problem is, when Rapidshare is actually unreachable, the returned error is an 
505
Timed-Out. When Rapidshare is up though, but the proxy is unreachable, the error
still is a 505 (as you seem to imply). Deleting the proxy then isn't fair, 
because
the possibility that the proxy does actually work but Rapidshare is down, 
exists.
I'll have a look at it later this week, maybe try something like a raw socket
connect. This'll show if the proxy is connectable, but won't show if it 
actually works.

Original comment by tim.besard@gmail.com on 7 Sep 2009 at 12:02