LinkStatus: new ERROR_IP_BANNED
|Status:||Waiting for Feedback||Start date:||09/14/2014|
|Target version:||020 - Next Release 2.0|
Many hosters block proxies, I'm seeing loads and loads of subnets blocked due to this. We need a more effective way to deal with this situation. Using error fatal is all and good, but if we have more direct error exception we can handle better!
When using default connection 'noproxy', we should assume that reconnection can not avoid restriction, covers 'datacenter/colo/vpn/vps provider/(isp) ip subnet'
When connection is from proxy, discontinue given proxy entry from use (add to session blacklist?). Effectively prevent retry with given connection type.
Also it would also be good applying to account level, for instance when someone adds account from 'datacenter/colo/vpn/vps provider/(isp) ip subnet', if we throw that exception it will mean disable account and throw generic message indicating your IP has been banned!