gnezim
8feb5de70e
The local WAF is unpredictable: some windows the gost VPN tunnel at 127.0.0.1:8888 is 503-ing (direct must work), other windows the direct IP is throttled to 403 by Ngenix (VPN must be used). The previous hardcoded `--noproxy '*'` survived one of those states only, which is why the dictionary load surfaced as console 403s as soon as the state flipped. Try direct first (faster when it works, simpler cookie jar), fall back through the system HTTPS_PROXY on 4xx/5xx or curl failure, keep a separate cookie jar per transport so the Ngenix cookies don't cross- contaminate edge nodes.