Environment
SaaS (https://sentry.io/)
Steps to Reproduce
Replay correctly records SSE requests in the network tab (status, duration, headers), but captures 0B of response body. Individual events pushed over the stream, connection duration, event count, and close reason are all invisible.
Expected Result
Event count, connection duration, and close reason captured.
Ideally: individual SSE event payloads visible in the Replay timeline.
Actual Result
SSE request appears in the Replay network tab with status 200, but response Body Size is 0B. No stream content, individual events, event count, or close reason is recorded.
Product Area
Replays
Link
No response
DSN
No response
Version
No response
Environment
SaaS (https://sentry.io/)
Steps to Reproduce
Replay correctly records SSE requests in the network tab (status, duration, headers), but captures 0B of response body. Individual events pushed over the stream, connection duration, event count, and close reason are all invisible.
Expected Result
Event count, connection duration, and close reason captured.
Ideally: individual SSE event payloads visible in the Replay timeline.
Actual Result
SSE request appears in the Replay network tab with status 200, but response Body Size is 0B. No stream content, individual events, event count, or close reason is recorded.
Product Area
Replays
Link
No response
DSN
No response
Version
No response