|
|
|
#1
10.10.2019, 23:59
|
|||
|
|||
If geoblocking is detected, add hoster to blacklist
I noticed that JD2 recognizes 403 geoblock for zippyshare - if a connection is detected as being geoblocked, why not ad zippyshare to the blacklist of that connection? - or at least stop reusing the same connection for that host until the next restart of jd2?!
|
|
#2
11.10.2019, 16:09
|
||||
|
||||
|
That's not that simple. For example the user might wanna use a multihoster to download from that host and being blocked will result in not using that connection at all. At the moment it's not possible for that fine tuned error/block handling. It requires new error states and controller supporting those
__________________
JD-Dev & Server-Admin
|
|
#3
11.10.2019, 18:11
|
|||
|
|||
|
Is it possible to show which proxy has been used so I can configure the blacklist manually?
|
|
#5
11.10.2019, 18:48
|
|||
|
|||
|
Oh, I should have mentioned its a headless JD - column selection is not possible via MyJD, right?
|
|
#6
11.10.2019, 19:02
|
||||
|
||||
|
I'm sorry but this information is not available to headless interface :( But you might wanna use the Eventscripter and automatically place ban to those connections/proxies where this happens, see https://board.jdownloader.org/showthread.php?t=70525
ask mgpai for further help. He's our script master script can check for 403 geo block message and try to add it to blacklist
__________________
JD-Dev & Server-Admin
|
|
#7
11.10.2019, 20:45
|
|||
|
|||
|
thx jiaz
|
 |
| Thread Tools | |
| Display Modes | |
|
|
Hybrid Mode
