This may cause several concerns, namely performance and legal (GDPR). Unless we also put special filters in place, this will affect every request, not only the specific requests we want to inspect more closely. However, for this we need to tap into the request processing pipeline after the request content is decrypted. We could instead intercept the traffic on the server. Also, obviously you need to really, really trust the application's author. It is rather invasive as the application messes with your network stack. The traffic will be captured on the phone, thus you need to run your analysis directly on the phone or send the recorded data off your phone before being able to analyse it.

Most apps require root access in order to capture traffic There are a few downsides to this approach: HTTP Canary ) on the phone, which will then hook into the phone's network stack. In this case the traffic gets captured right where it is generated, but before it gets encrypted. There are three places where we can tap into the mobile traffic: on the client, where the traffic is encrypted, on the server, where the traffic is decrypted, and/or on the line in between:ġ. In order to decrypt HTTPS traffic, one must be in possession of the correct key, which ultimately only the server knows (also hopefully). The biggest challenge for intercepting any traffic is end to end encryption (which hopefully everyone is using by now, except maybe TikTok ). To hopefully save you time, this post sums up my findings and describes possible ways and necessary steps to view and analyse your mobile traffic (valid at the time of this writing in April 2020). As usual it took quite some time and experiments to follow breadcrumbs on the internet, sort out the obsolete/expired information, and put together all the puzzle pieces to a complete working end-to-end picture. So I had to put on my hacker-hat and start some research on how to intercept HTTP packets coming from my phone. While I do know my share of TCP and HTTP, I am not hacking into mobile traffic on a day-to-day basis. This forced us to go a level deeper and investigate the problem on the protocol level. Only after a lot of experimenting we could narrow the problem down to specific mobile devices. Recently we faced an 'interesting' problem: We received seemingly random reports for failing logins to our customer's website.

Android emulator charles proxy mac