-
Notifications
You must be signed in to change notification settings - Fork 189
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Capture Traffic from Non-Proxy-Aware Apps Using ProxyMan #2131
Comments
Thanks for the tip about using the
May I ask if you have installed & trusted the Proxyman certificate on your iPhone? You can follow the instructions in the Certificate menu -> Install for iOS -> Physical Device. Or online at https://docs.proxyman.io/debug-devices/ios-device You can skip the 2nd step (Set HTTP Proxy Part)
I believe that you forgot to install & trust the certificate, so Proxyman can't open the SSL Connection. |
Yes, I have installed and trusted the ProxyMan certificate. The certificate appears to be configured correctly. When I follow the standard setup by changing the HTTP proxy settings, everything works as expected—I can browse HTTPS websites and see the requests in ProxyMan. However, I am unable to see traffic from non-proxy-aware applications with this setup. |
@NghiaTranUIT that would be fantastic, thank you! Proxyman's UI is incredibly clear and user-friendly—far superior to anything else I've used. If I can get it to work with non-proxy-aware apps, I'll happily delete all my other tools :) |
+1 I am able to capture browser traffic in Proxyman, but not traffic from other apps on my physical device. |
Would be very cool to have this feature |
I would like to use ProxyMan to capture traffic from non-proxy-aware apps. ProxyMan has a very user-friendly UI and works perfectly with proxy-aware apps, where I can set up an HTTP proxy on a mobile device and view traffic on a ProxyMan instance running on a macOS PC.
Current Setup:
iOS App: Does not honor HTTP proxy settings.
macOS: Running ProxyMan to capture traffic.
Steps Taken:
Observations:
HTTP Traffic: Successfully captured and displayed in ProxyMan.
HTTPS Traffic: Browser shows "can't establish a secure connection to the website."
Comparison with Burp Proxy:
Using Burp Proxy in invisible mode, HTTPS traffic is successfully captured and displayed.
It appears that Burp Proxy handles HTTPS traffic differently, even though the approach seems similar.
Request:
I understand that ProxyMan is primarily designed for HTTP proxying. However, I would like to understand what Burp Proxy does differently to handle HTTPS traffic successfully. It's also unclear why HTTP works successfuly, while HTTPS does not
Links:
The text was updated successfully, but these errors were encountered: