fix: accept explicit socks5h for one-shot health
Preserve configured proxy DNS semantics while reusing strict URL and loopback validation. Cover proxy forwarding, legacy socks5, and unsafe endpoints with offline tests; document the managed DoH boundary. Co-authored-by: GPT-6 <gpt-6@openai.com>
This commit is contained in:
1 parent
721cad42ce
commit
544dda7c85
3 files changed
+55
-41
No files matched your search
@@ -109,8 +109,9 @@ not used and there is no direct fallback. The request times out after 30 seconds
|
||||
| `ZAPRET_AUTOTUNE_FAILURE_THRESHOLD` | `3` |
|
||||
| `ZAPRET_AUTOTUNE_RECOVERY_COOLDOWN` | `30m` |
|
||||
|
||||
Configuration is parsed once per health invocation. The proxy must use `socks5`
|
||||
with a loopback IP or `localhost`, port 1–65535, and no credentials/path/query.
|
||||
Configuration is parsed once per health invocation. The proxy must use `socks5` or `socks5h`
|
||||
with a loopback IP or `localhost`, port 1–65535, and no credentials/path/query/fragment.
|
||||
Explicit `socks5h` uses proxy-side hostname resolution (encrypted DNS only with managed DoH configured); explicit `socks5` retains local DNS semantics.
|
||||
Video IDs must be 11 characters; durations and the failure threshold must be
|
||||
positive. Explicit empty values are invalid. Interval, consecutive-failure
|
||||
threshold and cooldown configure `managed monitor` (the one-shot command still
|
||||
|
||||
Reference in new issue
Block a user