Last ned Proxyman 26.0.0

✨ Features
- Apps: See which app sends each request, group traffic by app, and pin apps or enable SSL Proxying for them.
- HTTP/2: Capture and debug HTTP/2 traffic. Turn on Use HTTP/2 in Settings to get started.
- Connection Log: See connection steps, request and response headers, and errors to help find connection problems.
- Access Control: Choose which remote devices can connect to Proxyman. Allow all, block all, or allow specific IP addresses.

⚡️ Improve
- Updated proxy status and Advanced Proxy Settings to make your IP address, port, recording, and HTTP mode easier to find and change.
- Improved speed and memory use when capturing traffic, viewing Connection Logs, and working with many pinned requests.
- Added Copy Client Detection Diagnostics to the Help menu to help troubleshoot missing app names.
- JSONPath filters now explain why a filter was rejected instead of only showing no results.
- Updated Electron and other libraries to fix security issues.

🐞 Bugs
- Fixed: The cursor and text selection now line up correctly in the Scripting editor on Windows.
- Fixed: Saving a Scripting rule keeps the selected HTTP method instead of changing it to Any.
- Fixed: Scripting keeps renamed HTTP/1.1 headers, and HTTP/2 headers work correctly in custom columns and CSV exports.
- Fixed: The Client column stays visible after updating unless you choose to hide it.
- Fixed: Typing in SSL Proxying filters no longer changes selected rules, and Escape closes an open menu without closing the whole window.
- Fixed: Existing SSL Proxying rules can still be turned on or off when the free plan limit is reached.
- Fixed: Pinned requests no longer appear twice or stop updating, and deleting requests also removes them from Apps.
- Fixed: Sidebar search avoids duplicate domains and keeps matching pins and imported files visible after Clear.
- Fixed: Changing the proxy port keeps your recording and system proxy settings. Restore Default also reports when port 9090 is busy.
- Fixed: Compose correctly displays binary WebSocket messages and keeps its requests out of Remote Devices.
- Fixed: Failed WebSocket connections show the server IP when the server sends a response.
- Fixed: HTTP/2 handles large responses more reliably and retries with HTTP/1.1 when a server requires it.
- Fixed: Redacted logs and Workspace uploads remove local app paths that could reveal your computer username.
- Fixed: Log exports report write errors, saved logs keep the correct HTTP/2 version, and restored sessions avoid duplicate request IDs.