This likely won't affect too many average users, but if you happen to work in a business or university with an open wireless network that relies on an internal hostname within a domain for any redirection, you're in a bit of luck. Up until this point, there's been a bug in Android that makes it impossible for the system to resolve a hostname on a local domain to its proper IP address.
Here's the bug report filed by a user back in April 2010:
Shortly: When connected on WiFi to a network which specifies a domain name, hostnames in that domain do not resolve without appending the domain to the hostname.
As background, our university has a wireless network open to students so that the network itself is "open", not secured, but no traffic past the gateway is allowed prior authentication using a web browser. In particular, if you try to access any web page with a web browser before
authentication, you will always be redirected to https://joynet:443/login Only once you have successfully logged in on that page, all network connections work as you'd expect them to normally work.
The problem is that the hostname (in this case "joynet") cannot be resolved to its IP address. When I do ping to joynet on my laptop, it says it is pinging "joynet.joensuu.fi" [192.168.0.1]. If I do the same on Android phone, using Android Debug Bridge (adb), for "ping joynet" it says it cannot find the hostname. If I do "ping joynet.joensuu.fi", it pings correctly on 192.168.0.1.
And this brings the problem that since the joynet gateway HTTPS server only shows the login form when hostname "joynet" is used in the HTTP headers, it makes it impossible to use WiFi on such networks because logging in is not possible. (going to https://joynet.joensuu.fi:443/login or https://192.168.0.1:443/login simply causes a redirection to https://joynet:443/login)
It doesn't affect a huge majority of users, but it's certainly a problem for a few IT professionals as well as students/employees of some organizations. That being said, a Google employee has informed everyone today that this bug has been fixed and will rollout with the next major Android release:
Guys, it was a matter of prioritization and resources. We don't have people to put on every requested feature and we certainly were not idle during this time. I apologize it took so long.
I can't say what the next version will be (neither know it nor can discuss it) but it will be after 4.2, which has already gone out.
Of course, this means that the fix won't be a part of the 4.2 Jelly Bean update that just came out. Nor is it part of the previous Jelly Bean release that still only accounts for 2.7% of all devices so far. Of course, to keep this in perspective, most users haven't even encountered this issue, so it will be easy to suddenly care about the two-and-a-half-year delay fix to this bug and get in a huff, but that would be a little silly. However, it does highlight that even in a modern OS like Android, there are still things that need to be addressed, and even once a problem is fixed, it could still take a while for the update to rollout.