ProxymanApp / ProxymanApp/Proxyman
Slack Huddle connetction drops when the Proxyman traffic list was cleared
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 7k
- Forks
- 237
- PR merge metrics
- No merged PRs in 30d
Description
Description
Pre-condition: The Slack traffic was not proxied
Steps to Reproduce
- Start SSL proxying for the system
- Connect to Slack
- Start a Huddle
- Clear caching memory in Proxyman
- Observe the result
Current Behavior
The Slack Huddle connection was dropped. Slack tries to reconnect the connection
Expected Behavior
The "Clear cache" flow should not affect not-proxied traffic (or live traffic at all)
Environment
- App version: Proxyman Version 5.11.0 (51100) | macOS: Version 15.1.1 (Build 24B91)
- Slack App version: 4.41.98 0125a83d730fa63d7943a316f238101f4ff10b8c@1732084053 (Production)
- macOS version: macOS Sequoia 15.1.1 (24B91)
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 the issue using the listed macOS, Proxyman, and Slack versions: enable system SSL proxying, start a Slack Huddle, and clear Proxyman's caching memory. Trace the clear-cache flow and verify that clearing it leaves the non-proxied live Huddle connected; the issue provides no file or test entry point.
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
- Clearly specified
- Newbie friendliness
- 35/100