I recently had a . I was seeing intermittent issues with an app, Tapatalk , not working properly with a web forum hosted by a friend of mine. I knew there was a much better chance of getting the bug fixed if I could a) prove it was a bug and b) show the devs exactly where the was, but I was hampered by the usual : iOS apps are a bit of a black box and I couldn’t see what it was doing internally.

However, like almost all network-aware iOS apps, this one was clearly using a web service to get data from the backend. So, all I needed to do was figure out a way to see the traffic on the web service.

The first thing you need is an HTTP sniffer program. The grandaddy of all network traffic sniffers is Wireshark, but it’s rather low-level and overpowered for quickly looking through HTTP traces. It’s a bit like using an electron microscope when what you wanted was a magnifying glass. I came across several glowing references to Tuffcode’s MacScoop HTTP Scoop during my research, but didn’t really want to spend $15 on an app I was only going to use once. I settled on PortSwigger’s Burp Suite, a comprehensive HTTP tool. The free version has the HTTP Proxy feature, which is the only bit we need; grab that. ( users: you can use the excellent and free Fiddler Web Debugger, but I won’t be walking you through that today, sorry. The steps are very similar though.)

3883f5eb71r590px.jpg 450x281 How to inspect iOSs HTTP traffic without spending a dime

See the original post here:
How to inspect iOS’s HTTP traffic without spending a dime