Re: Unable to Capture Trafic from My Custom Mobile App from Android Emulator

[EricLaw]

How did you configure the Android Emulator's web browser to go through Fiddler?

 

What platform/language did you write your "custom build mobile application" using? Does that technology allow you to specify a proxy on Web Requests?

[Blackbox]

Eric

Traffic from Web Browser did go through fiddler.
I configure it using.
Settings->Wireless Networks->Mobile Network->access point->TelKila and the proxy settings
I following this link for it
http://aurir.wordpress.com/2010/03/22/tutorial-getting-android-emulator-working-with-fiddler-http-proxy-tool/



But this did not work is with my application(or even some other apps that i downloaded from net to check it)

My App is build in Java. and it is installed as .apk format.
How can i check that it allows proxy on web request or not?

I also try to check wifi settings but in emulator it did not work as Wiki network did not exist

[EricLaw]

My understanding is that, when debugging Android platforms that don't have a proper proxy setting, most developers are using a tool called IPTABLES to route their traffic through the desktop PC running Fiddler. That entails some special configuration steps (search this group for Android HTTPS) but seems to work for them.

[chup...@gmail.com]

I stopped fiddler on my computer after which I have sent an wahtsapp message. The message got through but the browser on my mobile is not able to communicate anymore.

 

This confirms my suspicion. I will root my device tomorrow and install the app that I mentioned earlier. I've seen it has a "global proxy" setting which I think will fix our problem.

 

I'll let you know how it went.

[chup...@gmail.com]

Iptables is just one of the most popular Linux firewall utilities. It runs in kernel space and since Android is Linux based it also runs, i guess, on Android devices.

 

They are probably using it to mangle traffic towards the proxy server. Although manually configuring it might prove to be a painful process. Plus you might end up filtering and mangling the wrong type of traffic if you hadn't had experience with it.

 

If anyone tries to manually do it let me know how it worked out for you. :)

[chup...@gmail.com]

Ok so I tried it. Apparently it works.

After rooting my device and installing proxy droid all traffic (including the traffic generated by applications) was routed through the proxy. However apparently the application that i am trying to analyze does not accept the Fiddler root certificate.

I tried installing the certificate on the device and it no longer produces certificate errors in the browser so it installed correctly. However I think that the application does additional checks against a restricted list of authorities, not taking into consideration the local certificate store.

But good news is that installing proxy droid will route all traffic through the proxy server. This should solve BlackBox's problem.

If you have any thoughts on how to fix the certificate thing let me know. I will try to reverse engineer the smalli code to see if I get any info on how the check is performed.

[Blackbox]

How i can run emulator as root? as i am not testing on device but emulator.

[Blackbox]

I try adb root
and it said already running as root
but proxy droid is not working even for browswer

although one time it works for the browswer but now it is not even working for browswer :(

[Blackbox]

I have make my Application hitting my proxy sever and use reverse proxy option of fiddler to redirect to the actual server. by this i am able to capture and fiddle with the request coming out from my application. So for the time being problem solved

But Eric please can you check what is the problem

[EricLaw]

I don't think I understand your question, Steven. You might want to start a new thread rather than resurrecting this one from April.

 

If you've configured Fiddler to change an incoming request URL and you allow that request to be sent from Fiddler, then when Fiddler reads the response from the new server, it is passed back to the client in response to the original request.