Captive portal detection in abrowser
- Login o registrati per inviare commenti
I am a translator!
When I connect to a wifi network using what is perhaps called a "captive portal", abrowser does not find it and then I can't use that wifi network. In "about:config", I saw that:
- network.captive-captive-portal.enabled is set to false
- captivedetect.canonicalURL is empty
Would the captive portal detection work if the first one is set to true and the second one to some appropriate URL (which one)?
I read that it is not possible to make an extension that modify those. Another solution could be a specific user profile, then one can start with the profile in which it is enabled, connect, close abrowser and start it again with the usual profile. Can anyone think of a more convenient solution?
This is turned off because captive portals can only be detected by making requests over the network. A project policy is that Trisquel should not make connections over the network on its own, especially just as a result of joining some random network.
What I do in these cases is go to any random site that's available over HTTP. The request usually then gets redirected to the appropriate location. I happen to have my own self-hosted server at home so I make sure that one of the domain names can be accessed over HTTP (i.e. that it's not force-redirected to HTTPS) just for this purpose.
I am a translator!
Thanks, I will try this next time. I just found http://httpforever.com that seems to be exactly for that purpose.
What do you think of the
http://httpforever.com/
Avron mentions? Is it safe to use that?
I am a member!
Any site that's available through HTTP will work for this purpose. Firefox by default uses the URL http://detectportal.firefox.com/canonical.html but as it's disabled by default I have this bookmarked for when I need to run it manually.