Proxy Check through Job Progression #1157
Replies: 2 comments
-
If you skipped this part and incorporated a bunch of nonsensical useless proxies into your job then all it will do is fail until you re-shuffle and never actually truly gets removed for good, unless I'm mistaken. Plus wastes a ton of time by continuously reincorporating bad proxies to try and fail on |
Beta Was this translation helpful? Give feedback.
-
Just check your proxies before starting the job, it doesn't take too long unless you set a high timeout, a low bot count or have hundreds of thousands of proxies. Also, a proxy might be banned on a given site and not on another one, so changing the status of a proxy to "Not Working" during the run of a given job for one target site might kill a proxy that wouldn't be banned on another site. Your use case is only valid for low quality free proxies, which does not cover all use cases. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
So currently you can run a proxy check, by sending tons of useless queries.
But what if make it at least not a complete waste of time, by also progressing the job in the process. What this means is, it takes the untested proxy, and actually proceeds to use it to completion on 1 check.
It only passes the test as a working proxy if it progresses.
And as a result, you also get rid of crap proxies that returned with the string you're looking for once, but doesn't accept followup queries
Beta Was this translation helpful? Give feedback.
All reactions