[CoovaChilli] Chrome on Android (https)
denis.dorigo at waveloc.com
Mon Sep 26 16:56:37 BST 2016
Thank you, but I do not fully understand... should we take the redirect
Did you see my video?
What do we do against this??
Waveloc Λύσεις Πληροφορικής
Phone: (+30) 2111980738 - 2111980092
Cell: (+30) 6940115120
From: CoovaChilli [mailto:coovachilli-bounces at brightonchilli.org.uk] On
Behalf Of Giovanni Bez
Sent: 26 September 2016 18:50
To: coovachilli at brightonchilli.org.uk
Subject: Re: [CoovaChilli] Chrome on Android (https)
yes i was getting in trouble with this issue but i think the right approach
is to avoid the redirect.. for example to get the captive portal screen we
use "Access to the wifi network" capability for the mobile when the device
detects an hotspot wifi network..
2016-09-26 17:41 GMT+02:00 José Borges <jose.borges at algardata.pt>:
> > Jose, did you actually check your installations with a Samsung
> > phone? One with Chrome installed?
> > They redirect to www.google.com and chrome converts via HST to
> > https://www.google.com.
> > The only way to bypass this ( a few times) is to clear the cache.
> [José Borges]
> As mentioned before this is own i have it setup at several hotspots,
> and until now its working.
> The browser opens, the www.google.com gets redirected to
> https://www.google.com, but since the DNS1 and DNS2 entry are not
> Google's, the customer gets redirected to the UAM portal.
> CoovaChilli mailing list
> CoovaChilli at brightonchilli.org.uk
CoovaChilli mailing list
CoovaChilli at brightonchilli.org.uk
More information about the CoovaChilli