ProxymanApp / ProxymanApp/Proxyman

Support websocket breakpoints, scripting and compose

Open
#2,088 3 comments 8 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
No language data
Stars
7k
Forks
237
PR merge metrics
No merged PRs in 30d

Description

Description

It appears that Apple has fixed the issue where websockets were not using the system proxy settings. I'm currently able to see websocket traffic again in Proxyman on an iOS 17.5.1 without using Atlantis.

Please add support for breakpoints and scripting for websockets with similar options to the existing feature, i.e. wildcard and regex support on websocket URL matching. Scripting allows automation of some testing scenarios, and would also allow the user to access sharedState variables that could be set outside of the websocket in the existing scripting frameworks. This would be really useful for those of us who have a hybrid websocket and API endpoint flow.

The ability to ignore ping/pong or heartbeat frames would be incredibly useful, so scripts would not have to run on each ping/pong.

In addition to breakpoints and scripting, compose would be very useful as well, to inject a frame onto the websocket in order to generate a response from the server for testing.

Why this feature/change is important?

Burp can do breakpoints, but the configuration and UI is terrible. It can't do scripting, and the whole experience is clunky and time consuming. Adding this support to Proxyman would greatly enhance it's feature set, especially if the breakpoints and scripts were located in the existing UI for those features, alongside API breakpoints and scripts.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the existing API breakpoint, scripting, and compose features and their shared UI, then compare how websocket traffic is handled. Done should include websocket URL matching with wildcard and regex support, breakpoint and scripting behavior, heartbeat-frame handling, and frame injection for compose.

Written by the indexing model from the issue text.

Assessment

Tech stack
ios
Domain
devtools, networking
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.