Force captive-net authentication
Force captive-net authentication
- Subject: Force captive-net authentication
- From: Fritz Anderson <email@hidden>
- Date: Mon, 16 Apr 2012 09:48:38 -0500
I have an iOS 5 app that does its networking business exclusively through NSURLConnection. My users will inevitably use a captive WiFi network.
The ones who are on the captive net report that the app goes catatonic upon net transactions. I've seen this before in other applications: The router intercepts the traffic and interposes (presumably) its login page, but the device never displays the page. The single SSID is used throughout a large university campus, and our networking people's policy is such that you may have to re-authenticate a couple of times a day.
It appears the captive-net API works the other way around, requiring that the app know the SSID it's looking for, and supply the credentials itself. This app will go out through the App Store, and can't know SSIDs in advance. Perhaps there's a way to finesse that, but it is not apparent to me.
Is there a way to get the authentication page to appear every time it's necessary? Can I use the magic URL the system uses to test for captivity? I'd assume I couldn't rely on that.
— F
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden