[kinqsradio]

Summary

• Found by trying it: with HTTP_PROXY (or ALL_PROXY, HTTPS_PROXY) set, a request through HttpApi to a loopback engine went to the proxy, bearer token included (the child got the proxy's 502). reqwest reads those variables by default and does not exempt loopback.
• HttpApi now builds its client with .no_proxy(). Redirects were already off.
• Test tests/no_proxy.rs: runs the test binary again as a child with the proxy variables set (and a NO_PROXY that does not name the engine) to a second listener; the proxy must get no connection and the engine must get the request. Without .no_proxy() the test fails.
• docs/device-client.md states the rule and lists the test.
• Trade-off: a machine that can reach the engine only through a proxy cannot use this client until a proxy setting is designed; the owner should know before an https engine is behind one.

Testing

• Full gate with Postgres: fmt, clippy, structure, wasm32, workspace tests (999 pass).
• Mutation: removing .no_proxy() makes a_proxy_in_the_environment_never_sees_a_request_to_the_engine fail.
• Not tested: the CI clippy toolchain (local only).

Co-authors

none

AI usage

• Written by hand, with no AI
• Harness and version: Claude Code 2.1.317
• Models: claude-sonnet-5-5 (all)
• Effort: medium
• Human role: set scope (reviewer's note on the builder)
• Sources: none

Checklist

• Works on Windows, macOS and Linux
• docs/architecture.md with any rule change; generated wire types with any contract change
• No copied source, secrets, credentials or personal data; no AI attribution in commits, title or branch