Skip to main content
Timeout semantics are consistent everywhere: the timeout bounds connection + headers (and, for non-streaming Converse, the full body read). For ConverseStream it applies only until headers arrive — the stream body is never bounded, so long generations are never cut off mid-stream.