There can be many ways captive portals work and it is tricky being able
to support the different ways of detecting this.
I've seen some offer redirects, but others offer different status codes
to indicate the captive portal, and not all captive portals act properly
once things get returned.
I would think this comes from network-manager level and not indicator
level.
** Also affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1571522
Title:
Detect captive WiFi hotspots
Status in Canonical System Image:
Confirmed
Status in indicator-network package in Ubuntu:
Confirmed
Status in network-manager package in Ubuntu:
New
Bug description:
Right now it is very annoying that when you connect to a captive wifi
portal, the device does not detect that. All other devices open the
log in page automatically, except ubuntu devices. One needs to
manually open the browser, type a url and get redirected before being
able to log in and start e.g. telegram messaging over the wifi
connection.
My proposed solution to solve this:
When a WiFi connection is established, indicator-network should do a http GET
call to ubuntu.com. If the reply turns out to be a redirect, it should open the
browser with the redirect url.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1571522/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
