I'm using Charles to sniff out the traffic on my iPhone at Starbucks and for some reason it won't work with at&t wifi. Google Starbucks wifi does, however. I use my iPhone to connect to the same wifi network that my MacBook is connected to. Then, for the proxy settings on my phone, I enter my computer's local IP address and the port that I specified in the proxy settings on Charles. I'm aware that some wifi networks block certain ports, but even when I change the proxy settings on Charles so that it's dynamic and it finds an open port, it still doesn't work. Any ideas?
IOS – Charles not working on iPhone at Starbucks
iosNetworkPROXY
Related Solutions
Use mitmproxy. It's proven for this sort of thing. A while back there was some uproar about the app Path uploading the adressbook to its servers. This was what was used to discover it. The guy wrote up how he used it and that's a nice intro on how to install and use mitmproxy.
From the site :
mitmproxy is an SSL-capable man-in-the-middle HTTP proxy. It provides a console interface that allows traffic flows to be inspected and edited on the fly.
mitmdump is the command-line version of mitmproxy, with the same functionality but without the frills. Think tcpdump for HTTP. Features
- Intercept and modify HTTP traffic on the fly
- Save HTTP conversations for later replay and analysis
- Replay both HTTP clients and servers
- Make scripted changes to HTTP traffic using Python
- SSL interception certs generated on the fly
Old question but for anyone else that hits this problem:
Within Terminal.app issue the command:
networksetup -setwebproxystate iPhone\ USB off
Afterwards, you can check that is disabled by using:
networksetup -getwebproxy iPhone\ USB
This should return Enabled: No Server: 127.0.0.1 Port: 8888
Best Answer
Client isolation. It is your enemy and your friend here. This makes it so not only can you not access your iPhone from your MacBook, but other devices on the network cannot access your MacBook or your iPhone either. There are a number of ways to implement client isolation on an
IEEE 802.3(Ethernet) network and even more ways on aIEEE 802.11(Wi-Fi) network, but they all essentially accomplish the same task - clients are only allowed to communicate with the access point and/or gateway.