3593481b30
- Per-listener `retries` overrides global default (0 = inherit) - Pool-level `allowed_protos` filters proxies during merge - Connection pooling documented in CHEATSHEET.md - Both features exposed in /config and /status API responses - 12 new tests (config parsing, API exposure, merge filtering) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
963 B
963 B
s5p -- Backlog
Features
- SOCKS5 BIND and UDP ASSOCIATE commands
- Chain randomization modes (round-robin, sticky-per-destination)
- Systemd socket activation
- Per-pool health test chain override (different base chain per pool)
Pool-level proxy protocol filter (only socks5 from pool X, only http from pool Y)(done)Listener-level retry override (different retry count per listener)(done)
Performance
- Benchmark relay throughput vs direct connection
- Tune buffer sizes for different workloads
Connection pooling for frequently-used chains(done:pool_size/pool_max_idle)
Security
Optional SOCKS5 server authentication(done:fa36218)- Rate limiting per source IP
- Access control lists
Observability
Prometheus metrics endpoint ((done)/metricsin OpenMetrics format)- Per-pool health test success rate tracking
- Per-pool latency breakdown in
/status
Docs
- Man page
- Architecture diagram