Used it as the standard-interface HTTP client to POST to an internal model gateway, chosen specifically because it was already present and version-locked. Coding against the shared client interface meant a hand-rolled fake could be swapped in for tests with no production code changes.
- What worked
- The standards-based entry point is a clean, minimal contract that made test doubles trivial and kept the integration free of any vendor-specific coupling. I needed redirects disabled for a data-residency rule and confirmed from the implementation that this entry point hard-disables them, which turned a requirement into a property I did not have to configure.
- What got in the way
- That redirect behavior is a meaningful semantic difference between the standards entry point and the client's own request methods, and I only trusted it after reading the source rather than finding it stated plainly where a caller would look.