Migrating from Proxyman

A map of Proxyman's tools onto Solpuga's and carrying a session over as HAR: what travels, what is lost, and the limits.

What maps to what

Proxyman and Solpuga both run on macOS, Windows and Linux. Where there is no equivalent, the cell is a dash.

Proxyman Solpuga
Map Local Map Local
Breakpoint Breakpoints
SSL Proxying List SSL Proxying: selected hosts only
Bypass Proxy List Bypass list
Copy as cURL Copy as cURL
Export → as HAR HAR 1.2 export
Opening a HAR by dragging it in HAR import, read-only
The host tree Grouping by host, application and device
The inspector Request and response inspector
The timeline Per-phase timing
Certificate → Install for iOS / Android Setup wizards: iOS (on macOS) and Android
Pin Partly: Pin Host, hosts only
External Proxying Partly: system proxy or PAC only, no authentication
WebSocket Partly: messages recorded, none sent
Map Remote Partly: via Rewrite
Scripting Partly: Rewrite, no code
Block List —
Protobuf —
Diff —
No Caching, Clear Cache —
HTTP/2 —
Command line —

Carrying sessions over as HAR

Proxyman both writes and reads HAR; so does Solpuga. Proxyman's own Proxyman Log has nowhere to go.

In Proxyman. Right-click a request → Export → as HAR (HTTP Archive). For a whole session, the same through the File menu. On macOS 5.20 and later there is also a command-line export, with a choice of format and domain.

In Solpuga. Tools → Import Session from HAR… (Cmd/Ctrl + Shift + I), or open the file from your file manager. It opens in a separate read-only window and leaves a live capture running. Files over 500 MB are refused.

What comes across

Headers, bodies, statuses and timings — everything HAR 1.2 describes. The imported window uses the same inspector as a live capture, and bodies and raw messages can be written out to files.

What is lost

  • Rules. Map Local, Breakpoint, the lists — HAR describes traffic, not settings. Rules get recreated, fastest from a request in a live capture, where the rule is filled in with the response that actually arrived. The HAR window does not create rules.
  • Scripts. Scripting is not in HAR, and Solpuga runs no code. Simple changes have to be redone as Rewrite rules.
  • WebSocket. HAR has nowhere to put it.
  • Protobuf. The decoded view does not travel, and there is no decoder here: application/protobuf shows as a binary body in hex.
  • Double decompression. Bodies in Solpuga's HAR are decompressed while the response headers are kept as they arrived, so some importers try to decompress again. Garbage instead of text is that.

What you get instead

An interface in English and Russian, and a free tier with no time limit.

View in Solpuga

Tool for this page

HAR viewerOpen a HAR file and read the requests, headers, bodies and timings.

Related