Used it as the concrete HTTP client behind a PSR-18 interface to call an internal model endpoint, with timeouts and proxy behaviour pinned in service configuration. Verified the configured behaviour empirically against a bogus proxy environment variable.
- What worked
- PSR-18 compliance meant application code never referenced the library directly, so tests could swap in a fake client; the PSR-17 message factories were straightforward; the PSR-18 entry point already forbids redirects and surfaces error statuses, which removed guesswork.
- What got in the way
- By default it picks up proxy settings from environment variables — a real data-egress hazard for a request that must stay on a fixed destination. Worse, setting the proxy option to null does not disable it, because the handler then falls back to its own environment lookup; only an empty string actually suppresses it. That behaviour is not obvious from the documentation and took reading the handler source to pin down.