Skip to content

Fix .no_proxy() on wrong client, clarify naming and remove redundant state#1

Merged
Haut merged 1 commit into
masterfrom
fix/proxy-client-cleanup
Feb 28, 2026
Merged

Fix .no_proxy() on wrong client, clarify naming and remove redundant state#1
Haut merged 1 commit into
masterfrom
fix/proxy-client-cleanup

Conversation

@Haut
Copy link
Copy Markdown
Owner

@Haut Haut commented Feb 28, 2026

Summary

  • Fix: Moved .no_proxy() from the request-builder client (where it had zero effect) to pool::build_client() where requests are actually executed. Previously HTTP_PROXY/HTTPS_PROXY env vars would silently route all upstream traffic through a proxy.
  • Cleanup: Removed stored target_url: Url from ProxyHandler; replaced with pre-computed base_path: String to eliminate redundant URL representation (target_url, target_base, and host_header were three overlapping derivations).
  • Rename: rate_micro_per_nsrate_per_sec — the field stores raw tokens-per-second, not microtokens-per-nanosecond. Updated doc comments to match.

Test plan

  • All 46 existing tests pass (28 unit + 18 integration)
  • cargo clippy -- -D warnings clean

…state

- Move .no_proxy() from the request-builder client (where it had no
  effect) to the slot clients in pool::build_client() where requests
  are actually executed. Previously HTTP_PROXY/HTTPS_PROXY env vars
  would silently proxy all upstream traffic.
- Remove stored target_url from ProxyHandler; store pre-computed
  base_path string instead, eliminating redundant URL representation.
- Rename rate_micro_per_ns to rate_per_sec — the field stores raw
  tokens-per-second, not microtokens-per-nanosecond.
@Haut Haut merged commit 6c4cd7a into master Feb 28, 2026
1 check failed
@Haut Haut deleted the fix/proxy-client-cleanup branch February 28, 2026 18:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant