Menu
On Android devices, our captive portal launches in Android's Captive Portal Browser. After authentication, we redirect the user to a status page, where they can see their session information, remaining time and data, etc. Most users choose to keep this page open.
The problem is that the status page redirect happens within the Captive Portal browser, which will eventually close. Is there any way that we can open the status page, in a 'full' browser, form within the Captive Portal browser?
Most of the relevant Android code seems to be in CaptivePortalLoginActivity.java. The mBrowserBailOutToken variable looks interesting but I don't see how we can get the token.
Any other ideas on how to handle a situation like this would also be appreciated.
433
What is Com. captiveportallogin? To answer your question, it is the Captive Portal Login app's Android package. It is responsible for the authentication of WiFi networks. Think about all the times you've tried connecting to free WiFi networks - you would have seen a web page asking for login information.
The captive portal feature is a software implementation that blocks clients from accessing the network until user verification has been established. You can set up verification to allow access for both guests and authenticated users.
Close everything in your browser. If you have your startup setting “Continue where you left off”, then change it to “Open the new tab page” and open your browser again. If you don't see the captive portal come up, try going to a http:// website as they can trigger the captive portal.
Captive portals were detected using cleartext HTTP probes to known destinations (such as connectivitycheck.gstatic.com ), and if the probe received an HTTP redirect, the device assumed that the network was a captive portal.
I don't think it is possible.
The mBrowserBailOut variable is set to a random number so you have no change to know that one from within the captive portal page.
Only if the redirect URL contains this variable it bails out.
The variable is used in cases there is an SSL error, so in case you have such, it would prompt the user to use the default browser.
EDIT: I mean what is funny, is that the URL only has to contain the token somewhere. So in theory you could make up an URL that contains all the possible tokens.
Long.MAX_VALUE is 9,223,372,036,854,775,807.
So that are far too much possibilities that fit into an URL, despite that fact that smaller numbers are already contained in larger ones.
117
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
