In other words, we need to implement M an-in-the-Middle- attack on our own network.Īs you can see, sniffing HTTPS traffic is a multi-step task, so in order to simplify my life as much as possible, I use Charles Proxy.
Therefore, the HTTPS proxy should also provide an SSL certificate., which is needed to work with HTTPS traffic. The hitch is that the HTTPS protocol was created so that, apart from the client and the server, no one could read what is being transmitted in HTTPS requests. In addition, we need an HTTP / S proxy server, with which we would look at / modify the traffic going through the iOS device.Īnother very important task is to be able to sniff HTTPS traffic. To read the traffic of an iOS device, we need to make it go through our Mac. Traffic goes from the iOS device through the router to the server, regardless of the computer traffic. Suppose your MacOS computer and iOS device are on the same local network, which looks like this:
One way to check what went wrong is to see the JSON that the server returns to you. Ī bug has come that instead of two items on the list of permitted morning meals, the application only shows one. The server in this case is Dropbox, and JSON can be viewed here. The application receives from the server JSON type: Depending on the time of day, it shows the user what to eat. Take, for example, the very simple FoodSniffer iOS application. Hi, my name is Andrei Batutin, I am a Senior iOS Developer in DataArt, and today we will sniff the HTTPS traffic of your iPhone.
0 kommentar(er)
