3 ms·
But that would be exactly the use case here; browse google manually and then hsts kicks in from then on. Later, I get a captive portal wifi and it uses http://w
by chinathrow 10y ago
But that would be exactly the use case here; browse google manually and then hsts kicks in from then on. Later, I get a captive portal wifi and it uses http://www.google.com/generate_204 http://www.google.com/generate_204 and whoops, no request sent and no way for the wifi to redirect me to their login portal.
Both happens in chrome hence the same browser context.
- icebraining 10y agoAh, right; I was thinking about the detection mechanism (which probably doesn't use Chrome), not the redirection.
- chinathrow 10y agoRight, the detection mechanism is part of the OS, not the browser. https://developer.android.com/reference/android/net/ConnectivityManager.html https://developer.android.com/reference/android/net/Connecti...