ProxymanApp / ProxymanApp/Proxyman
Websocket responses are corrupted the next day in an open ProxyMan
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 7k
- Forks
- 237
- PR merge metrics
- No merged PRs in 30d
Description
Description
Lost responses in the WebSocket traffic after some time period
Steps to Reproduce
- Capture a piece of traffic that contains WebSocket
- Leave Proxyman Open
- Check it in one day
- Some responses will be corrupted (trimmed)
Current Behavior
If I capture WebSoket traffic (socket.io) and leave Proxyman open (without saving the session to the file), the next day, I discover that some of the answers have been cut off (only the beginning remains of them)
For example, instead of the entire Response (JSON), I found only this:
42["response",
I saw you asked in some thread "is there "..." symbol in the end - answer is "no"
I even exported this message as a file and saw the same in this file.
Expected Behavior
Environment
- App version: Proxyman Version 5.19.0 (51900) | macOS: Version 15.3.2 (Build 24D81)
- macOS version: MacOS Sequoia 15.3.2 (24D81)
- MacBook M3 Pro
Contributor guide
No contributing guide indexed for this repository
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
Reproduce with captured WebSocket or socket.io traffic in Proxyman 5.19.0 on macOS Sequoia, leave the app open for a day, then inspect the responses and an exported message. Done means responses remain complete rather than being trimmed to content such as 42["response",.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- desktop, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100