Used it first as a control to prove the network was fine when the vendor SDK's auto-discovered client was failing, then wired it in explicitly as the HTTP transport for the long-running streamed API call so the timeout semantics were ones I chose rather than inherited.
- What worked
- Dropped in as a standards-compliant client with no configuration. Timeout options are named clearly enough that it was obvious which knob controls idle gaps versus total duration — exactly the distinction that had bitten me with the auto-discovered alternative. Useful as a quick isolation test because a five-line script gives a definitive answer.