I only ask because I'm curious what this will do with captive portal nonsense.
I only ask because I'm curious what this will do with captive portal nonsense.
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.
It's a light funny page i've found about 10+ years ago but it's HTTP and helpfull for captive portals.
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.
It makes sense to keep falling back to HTTP if that header is not set.