[Replay] SSE (text/event-stream) response body not captured - 0B recorded despite successful stream
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 21h 23m
- Merged PRs (30d)
- 607
Description
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with an SSE (text/event-stream) response in Replay and trace the existing network capture path. Done means the Replay network entry records the stream's event count, connection duration, close reason, and response body size; individual event payload visibility is the stated ideal.
Written by the indexing model from the issue text.
Assessment
- Domain
- observability-sre
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100