mirror of
https://github.com/ProxymanApp/Proxyman.git
synced 2026-04-26 08:35:53 +03:00
[GH-ISSUE #875] Proxyman not capturing traffic from command line apps #871
Labels
No labels
Discussion
Feature request
In Progress...
Plugins
Waiting response
Windows
Windows
bug
duplicate
enhancement
feature
good first issue
iOS
macOS 10.11
question
wontfix
✅ Done
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Proxyman#871
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @paul-go on GitHub (May 3, 2021).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/875
Originally assigned to: @NghiaTranUIT on GitHub.
Proxyman version? (Ex. Proxyman 1.4.3)
Proxyman 2.24.0
macOS Version? (Ex. mac 10.14)
macOS 10.13
Steps to reproduce
I'm not sure if this is a supported feature.
I'm trying to inspect the HTTPS traffic going through the wire that is being originated by the restic command line tool, but the traffic doesn't appear to be capturing in the side bar. I have HTTPS traffic being captured that is originating from other desktop apps installed install on this machine.
I even have the domains of interest both "Pinned", however, the only requests that are showing up are the ones that originated from CyberDuck:
I also tried to add the restic executable file directly as an app ... it doesn't appear that this is supported (the option to choose this file is disabled in the open file dialog)
@NghiaTranUIT commented on GitHub (May 4, 2021):
Hi @paul-go You could not see the HTTP traffic from the command line app because their traffic doesn't go through the HTTP/HTTPS Proxyman Proxy Server (at localhost port 9090).
To illustrate, by default,
curldoesn't send a request to Proxyman unless we explicitly config it with--proxy http://localhost:9090To fix your problem, we have to know what CLI you're using? Then let see if this CLI supports HTTP/HTTPS Proxy config.
curl)@NghiaTranUIT commented on GitHub (May 4, 2021):
One solution I can find to force all CLI apps that go through HTTP/HTTP Proxy is using
http_proxy/https_proxyflagRef: https://www.serverlab.ca/tutorials/osx/administration-osx/configuring-a-network-proxy-for-osx/
@paul-go Please try it and let me know if it works for you 😄