Thursday, April 19, 2012

What's the taste of the ice cream on my sandwich? How Android 4.0 ICS improves (not so much) the handling of Wi-Fi proxy

Hi Guys! I know it's been a long time since my last post. I'm sorry but, while I was waiting to receive some answers on Android Proxy, I decided to spend an entire month exploring alternative ways of seeing the world around me.

Anyway, let's get back to work. Since I'm preparing a big summarizing post regarding the proxy support (be prepared!), I decided to write a more simple post, just to stretch my hands... 

Today I want to go back to the users (hey guys, I never forgot you!!), talking about what Android 4.0 ICS (Ice Cream Sandwich) changed regarding the Wi-Fi proxy handling.

To be honest not so much, just the addition to the default browser (and starting from yesterday also the latest version of Chrome) of the credentials for authenticated proxies, BUT unfortunately no changes on the API. So all the developers that want to handle authenticated proxies have to work with their hands at low level.


Just I did for Honeycomb devices, I'll show with a lot of screenshots, how to configure the Wi-Fi Proxy Settings in a Android 4.0 devices, so you can easily understand how to do it. Only a small change has been introduced since Android 3.1, but It's worth to be explained in full details! Are you ready? OK, let's start then!!

First, open the Wi-Fi settings. 


Touch and hold the access point you want to configure the proxy setting:


Select the "Modify Network" option from the "Configuring AP" dialog:


Your device will show the configuration settings for the selected AP:


Check the "Show advanced options" option:


 Select "Manual" option from the Proxy settings drop-down list:


The window will now show the proxy settings of the selected AP:


You just need to edit it:


And save it:

 

And it's done! Easy right? Perfect!

Ready for the new surprise? As I previously said the default Android browser supports also the authenticated proxies, so when you will try to navigate to your favourite site, you will be prompted to enter User and Password.. 


Et voilĂ , you can now navigate with the default Android browser behind your authenticated proxy.




The work for the end users is really simple. But please be careful! As you can see from the screenshots, the configuration AP window explicitly says that:
"The HTTP proxy is used by the browser but may not be used by the other apps".
This means that it's the duty of the developers of your favourite apps to support this configuration, reading it, and using it for every HTTP connection. How do they can do it? APL could be a nice option to try out. It's still in an early stage, but I promise to give it a boost in the next weeks, so stay tuned! If your favourite app doesn't support the proxy settings, please write to the developers and point them out to this website! They can follow my instructions and add the proxy support in no time!

By the way, starting from today I can officially announce that this site hosts also a discussion group, so all the users can share their problems, findings, requests, or any other useful information. I'm looking forward to hearing your experiences!


So please don't be shy! I'm waiting for your contribution!