NeverSSL
11–20 of 206 posts
I miss the old purple page at purple.com which unintentionally served the same purpose. Comcast techs used to use it as a test for whether you were in their captive portal.
Re: NeverSSL
#12Re: NeverSSL
#13Re: NeverSSL
#14Any idea why http://neverssl.com redirects to http://{random_characters}.neverssl.com?
Re: NeverSSL
#15I use captive.apple.com if a public network fails to load the login/getting-started page.
I used the same until I recently hit a network that allowed that site but was captive for everything else. No idea what would inspire that configuration.
Re: NeverSSL
#16Any idea why http://neverssl.com redirects to http://{random_characters}.neverssl.com ?
Avoid caching.
Re: NeverSSL
#17I use captive.apple.com regularly but just realized that https was the issue being worked around on WiFi. Learning something new.
What do you mean by "the issue being worked around"?
The issue is that https cannot be intercepted by such an access point, and is increasingly popular for all types of web use. "Being worked around" makes it sound like something different, perhaps even sinister.
Re: NeverSSL
#18Any idea why http://neverssl.com redirects to http://{random_characters}.neverssl.com ?
Probably avoid caching. Just taking a guess, but you do not want your DNS cached when the poorly-programmed router login page is trying to spoof DNS, and redirect you to their login portal.
Re: NeverSSL
#19Any idea why http://neverssl.com redirects to http://{random_characters}.neverssl.com ?
Apparently because ISPs sometimes muck with caching headers? https://twitter.com/NeverSSL/status/1136491293113180160
Re: NeverSSL
#20Then there is http://uselessaccount.com/