We battle this one quite often. Here are a couple thoughts: The apple devices, when they attach a wireless, automatically call the "success" page (randomdomain/library/test/success.html) on the apple domain. The idea is nice, because it should autoopen the captive portal page as it tries it's http "success" page call To get there it chooses from multiple domains. There is quite a large list, some are shown here: ios - ios7 and captive portals-changes to apple request URL - Stack Overflow. Having said that, I have found that even minor changes in the OS act differently. (example not necessarily correct) IOS 6.01 works, 6.02 doesn't, 6.03 works sometimes etc. As I recall, the primary issue is related to Safari. I had a case with Palo Alto where we did packet captures, etc and Safari would try to get out but would never get any packets back. As I recall, we never did figure out why. Firefox and Chrome work without a problem. So what I ended up doing is Creating a rule to allow unknown user access to the apple subnet and the success page. Effectively disabling the captive portal auto prompt. Made it clear to my users that if they have an issue with IOS devices, try using a browser other than Safari and it will work every time and they will not get any email, or apps, functioning until the open a browser window. When they open safari or chrome, make sure to go to an http page. Google, for example tends to default to https. I may not have the above 100% as it has been a while, but hopefully that will give you some starting points. Bob
... View more