The Capture tool is at the core of AppBandit proxy. It is responsible for configuring, starting and stopping proxies and displaying captured data. This is the tool where you will spend most of your time working with.

To get started you need to define at least one feed. Feeds are the means by which you instruct the tool the type of channel you want to monitor. Feed URIs prefixed with "proxy://" protocol refer to the local proxy server. For example, to spawn a proxy server on "localhost" port "9191" the feed URI "proxy://localhost:9191". You can also bind to any of your network adaptors' IPs. For example, the feed URI "proxy:// will start the proxy on the local network IP port 9191. Clients on that network will be able to connect to the proxy on that address.

You can also connect to a WebSocket feed giving AppBandit a great way to interoperate with existing tools. One such tool is Pown Now form the Pown.js framework. Once configured, Pown Now will sniff a network interface and forward data to the specified WebSocket address. AppBandit can consume this data and display it as part of the proxy history.

The traffic accumulated by the proxy can be sometimes overwhelming. This is why it is essential to think about what you want to capture and what you would like to ignore. This is controlled by the scope settings. You can select multiple scopes or no scope at all before start recording.

Once you have a feed and some scopes defined and selected you can begin recording by pressing the Record button. Immediately you will notice data being captured in the transactions grid. All relevant request and response parts are parsed for your convenience and you can use various filters to sort through the data.

If you no longer need the proxy, press the Record button again to stop it. Making changes to the scope or the selected feeds requires for the server to be stopped if already running. Remote agents which provide feeds do not need to be restarted unless advised otherwise by the tool vendor.