Chrome’s address bar will use https:// by default

Re:Chrome’s address bar will use https:// by default by TimBurr on Tuesday March 23, 2021 @12:42PM (#26557050)

I've found http://neverssl.com very helpful for captive portals. It does what you'd expect - hosts a HTTP-only page that allows captive portals to work correctly.

Since it's only ever HTTP, it sidesteps the certificate errors or HTTP downgrades that normal sites are hit with during captive portal interception.

I am curious what happens to captive portals as HTTPS adoption rises. Some OS's (Android, OSX) already detect captive portals and launch a lightweight webview.

[ Parent | on HN ]

Re:Chrome’s address bar will use https:// by default by banana_giraffe on Tuesday March 23, 2021 @12:56PM (#26557229)

Yep, I use neverssl.com, when I remember it. Though, mostly I use example.com, since that works without SSL as well. I guess now I'll need to remember to type http://example.com .

Based off my experience, more and more captive portals appear to be letting the requests the OS makes to captive.apple.com or whatever through but still try to present a captive portal to the user. I can guess as to the motivation, but as a user it's danged annoying.

[ Parent | on HN ]

Re:Chrome’s address bar will use https:// by default by xeromal on Tuesday March 23, 2021 @12:47PM (#26557112)

Thanks for this. I never can remember URLs like this but I always remember chicken.com. It's sad day to see it go away.

[ Parent | on HN ]

Re:Chrome’s address bar will use https:// by default by rnotaro on Tuesday March 23, 2021 @01:17PM (#26557469)

I'm French-Canadian I use http://perdu.com [1] (Perdu is lost in French).

It's a light funny page i've found about 10+ years ago but it's HTTP and helpfull for captive portals.

[1] https://fr.wikipedia.org/wiki/Perdu.com

[ Parent | on HN ]