Captive WIFI portals suck.
So often when I open in a browser (Desktop Chrome or Mobile Chrome) a HTTP site, I get the captive portal, but with auto-completion and so quickly I connect again to WIFI.
The problem is that after the captive portal redirects, I'll have also a HTTPS redirect and Chrome remember the certificate and to use only HTTPS. So I cannot use the same site twice (in a session).
A well-known public HTTP only site will resolve this. Well-known sites usually work, causing some less debugging of the WIFI connection.
22 Answers
A well-known public HTTP only site will resolve this
You can use :
5What?
This website is for when you try to open Facebook, Google, Amazon, etc on a wifi network, and nothing happens. Type "" into your browser's url bar, and you'll be able to log on.
How?
neverssl.com will never use SSL (also known as TLS). No encryption, no strong authentication, no HSTS, no HTTP/2.0, just plain old unencrypted HTTP and forever stuck in the dark ages of internet security.
Why?
Normally, that's a bad idea. You should always use SSL and secure encryption when possible. In fact, it's such a bad idea that most websites are now using https by default.
And that's great, but it also means that if you're relying on poorly-behaved wifi networks, it can be hard to get online. Secure browsers and websites using https make it impossible for those wifi networks to send you to a login or payment page. Basically, those networks can't tap into your connection just like attackers can't. Modern browsers are so good that they can remember when a website supports encryption and even if you type in the website name, they'll use https.
And if the network never redirects you to this page, well as you can see, you're not missing much.
These answers came from the comments and I believe they need a separate entry in the answers so they can be easily found.
(from @GiantTree)
(from Virtually Nick)
NeverSSL did not work in my ISP's captive portal but the one from Google did.
