Currently Being ModeratedSep 20, 2012 7:21 AM (in response to Yogiee)
The logic Apple's code seems to be using is:
1) Connect to Wi-Fi
2) Try going to a known apple.com web page
3) If that fails, you must need to login to the Wi-Fi router so display the login page that would normally come up when a router redirects the request to the Apple web page somewhere else
Normally the Apple web page access would only fail if you failed to login to through the router's login page.
This is horrifically convoluted logic and is at best a hack rather than a real deterministic solution for just the reason you cite, namely if apple.com is down for whatever reason, no one with iOS 6 will be able to connect to their Wi-Fi networks.
Currently Being ModeratedSep 20, 2012 3:51 PM (in response to William Kucharski)
I agree, this way of doing things seems completely half-thought. I do get the logic behind their reason, believe me, the only part I don't understand is, what they changed in iOS 6's WiFi behavior that started causing the problem. If my information is correct, this method was being used since long before even iOS5. But it never caused the issue, specifically booting the device out of the network behaviour. I hope iOS engineers are reading this, cause this is really hampering my experience with iOS6.
I'm hoping my local ISP gets the cache server fixed soon (but knowing them, I am not sure when soon is soon enough), but that's a not a right of way doing the things.I hate to sound like broken record at this point, but unless the underlying issue with this method is fixed quickly, this can be really a problem for people who are just interested in using WiFi network without internet connection.
Currently Being ModeratedSep 20, 2012 4:01 PM (in response to Yogiee)
Apple may not have necessarily changed anything; rather it may simply be a case of access to that page has never failed before.
For example, if your ISP's cache server wasn't broken, you'd likely never know what happened "behind the scenes" when you tried to connect to your access point.
Still, now that we know it seems ripe for denial of service attacks, especially if an attack on apple.com could theoretically disable Wi-Fi access for all iPhone owners worldwide…
Currently Being ModeratedSep 20, 2012 4:05 PM (in response to William Kucharski)
No, I believe it's iOS6's issue. Because, the cache server of my ISP started giving issues about 3-4 weeks ago. Most of the issues got solved within a week or so, but there are still couple of sites that are inaccessible. Fortunately though, the cache issue seems to affect only www.apple.com, and not other apple subdomains, like support.apple.com or discussions.apple.com etc. I'm currently connected to this same bad-cache-server connection and able to post here, but can't access main www.apple.com site.
My point is, when I was on iOS5, despite www.apple.com failing, my iDevices didn't drop the WiFi. This started only after switching to iOS6. My old iPad1 WiFi version has no issue staying on the WiFi. Only devices with iOS6 are facing this problem.
Currently Being ModeratedSep 20, 2012 4:10 PM (in response to Yogiee)
Hmmm, then it sounds like Apple changed the method they use to determine redirects in iOS 6; interesting.
FWIW, the actual page iOS tries to reach is this one.
Currently Being ModeratedSep 27, 2012 2:33 AM (in response to Yogiee)
As of today, my ISP's cache server seem to have resolved the issues I had reported to them and with that www.apple.com is now working fine on my primary internet connection. This solved the WiFi captive url/portal login window issue. However, this still doesn't solves the root cause of the issue. Hopefully, we'll see some fix about this in next iOS6 update and hopefully soon.
Currently Being ModeratedDec 23, 2012 3:35 PM (in response to Yogiee)
This is a problem for me - my ADSL has been down for 2 weeks now and so far Telstra haven't been able to fix it... that's another story.
So my iPad2 can connect to my wifi network no problem, and I have a proxy server configured (without authentication). So I can see the iPad2 request for the www.apple.com site and of course it will never be reached while my ADSL is down. So when this request fails the iPad2 simply disables the wifi connection.
How do I get the iPad2 to ignore the fact that it has no internet connection?
My application development requires a web server on a local Linux machine, so my development has stopped because I can't get the iPad2 to stay connected to the local wifi.
Currently Being ModeratedDec 23, 2012 7:35 PM (in response to murray205)
Unfortunately, there doesn't seem to be any way unless somehow create a fake apple.com redirect on your network and place the success.html in an exact path (apple.com/library/test/success.html)... or edit your hosts file to redirect the apple.com to your local webserver. I know it sounds ridiculous, but unfortunately that's what it is currently with iOS6. Even the 6.0.1 update didn't fix it.
I'm still having issues with my ISP's cache server refusing to resolve Apple.com once in a while and whnever that happens all my iOS6 devices refuse to stay on my WiFi network, making it impossible for me to use any of my home network services (Air Video, iTunes media server and AirPlaying the stuff to my HTPC etc.).
Apple really needs to fix this issue as currently, it's impossible for the users to use their iDevices (with iOS6) on their OWN WiFi networks without internet connection. My old iPhone 3G, iPod touch and first gen iPad work just fine, only the iOS6 devices are suffering.
Currently Being ModeratedDec 23, 2012 8:13 PM (in response to Yogiee)
Exactly - in fact just after I posted I thought of the same solution - define a hosts entry for www.apple.com on my proxy server and download the really complicated 'success.html' file from apple. It certainly isn't rocket science.
So I have it working - iOS6 is completely fooled by my dummy 'success.html' file an is now working on my internet-less wifi network.
PS Just had the 2nd Telstra technician here checking the lines and connections... more adjustments and changed to different lines, and still no internet. It has to be something at the exchange end - it is ADSL syncing and receiving a dynamic IP, logging in and then about 6 seconds later the ADSL connection just drops out. The technician's modem (which doesn't login) remained connected without any problem. Not much chance of it being fixed in time for Christmas now - we've got less than 3 hours of work time left before everybody goes home to wait for the man in the red suit. And somehow I don't think Santa will be able to deliver me internet for Christmas.... (sigh)