As the OP said, that is already in iOS - it is just that more and more captive portals are whitelisting the domains it hits to check for a captive portal.
> captive portals are whitelisting the domains it hits to check for a captive portal.
Why?
As the OP said,
> ...so iOS will think it is connected to a good network... The stated reason for this stupidity? The mini-browser that pops up doesn't work with their stupid captive portal login or payment page.
It doesn't work so well. Sometimes I have to try every single browser on my phone or tablet and different sites. Eventually one of them triggers the captive portal detection. Sometimes I just give up.
Any Android from 4 to 7. I guess it depends on how much the portal is trying to be smart.
Re:NeverSSL
by keeperofdakeys on Wednesday January 11, 2017 @10:09AM
(#13374396)
Getting it working correctly can be annoying. There is actually a HTTP status code for captive portal redirection (511), but nothing supports it. So if you use it, captive portal detection stops working.
Apple already has captive portal detection, but it doesn't redirect to a whole browser - it just displays a mini browser with a Safari WebView.
Re:NeverSSL
by raverbashing on Wednesday January 11, 2017 @05:06AM
(#13372899)
Yes, Android 6.0 will be extremely annoying when trying to get you to click the captive portal.
There is no reason why Apple can't add captive portal detection at OS level like Android does.