TokenReply

Loading…

Reload

Streaming parser shows empty output

The HTTP stream may be valid while the client reads the wrong event field or stops before the final content arrives.

Last checked · Sources: TokenReply code and documentation review; upstream wording may vary

Area
Streaming
Typical response
HTTP 200 with unusable client output
Retry?
No, fix parsing first

Symptoms

  • Non-streaming succeeds but streaming appears blank.
  • Raw event data contains chunks the application ignores.

Likely causes

  • The parser assumes one provider’s SSE shape or treats an early metadata event as completion.
  • A proxy buffers, rewrites, or closes text/event-stream responses.

How to diagnose

  • Capture a redacted raw stream and inspect event order.
  • Confirm Content-Type is text/event-stream.
  • Compare the same request with stream false.

Fixes

  • Parse the endpoint’s documented delta events and terminal marker.
  • Ignore metadata-only chunks without ending the response.
  • Disable proxy buffering for SSE when required.

How to verify

The client accumulates content through the terminal event and matches the non-streaming answer shape.

Resources