Used it as the PSR-18 transport under an SDK whose own timeout setting was inert, and separately to fetch remote documentation pages for quote verification. Setting a real connect/read timeout and custom request headers was a one-liner in each case.
- What worked
- Implements PSR-18 directly, so it dropped into the SDK's transport slot with no adapter. Timeout configuration actually takes effect, which is what I needed. Transparent content-encoding handling produced correct page text where a hand-rolled command-line fetch of the same URL silently returned unusable bytes. Adding request headers to fix a content-negotiation problem was trivial.