Earlier quoted context omitted.
http://captive.apple.com/ also. That's what Apple devices use when trying to present the login for a captive network.
Is that better in any way than using example.com?
NeverSSL
21–30 of 212 posts
Re: NeverSSL
#22Re: NeverSSL
#23Earlier quoted context omitted.
Is that better in any way than using example.com?
If I regularly used that as a known-good site that should be up with no SSL, I'd trust that an apple-maintained site (backed by akamai) would be up before "example.com". I'm sure there are plenty of others, but someone might remember that URL over another so I thought it would be helpful.
Re: NeverSSL
#24Re: NeverSSL
#25Re: NeverSSL
#26Ah something for the day xkcd[1] makes https mandatory. 1. http://xkcd.com
Re: NeverSSL
#27Earlier quoted context omitted.
http://captive.apple.com/ also. That's what Apple devices use when trying to present the login for a captive network.
You can also use http://detectportal.firefox.com/ that we set up for FirefoxOS captive portal detection.
Re: NeverSSL
#28Earlier quoted context omitted.
Is that better in any way than using example.com?
If I regularly used that as a known-good site that should be up with no SSL, I'd trust that an apple-maintained site (backed by akamai) would be up before "example.com". I'm sure there are plenty of others, but someone might remember that URL over another so I thought it would be helpful.
Re: NeverSSL
#29So, this is for use captive wi-fi portals that are served over HTTP that would otherwise not work when initially connecting to a site using HTTPS?
It's especially relevant now that Chrome is threatening a big unsecure site warning for HTTP pages, so many sites which don't strictly need security are going to switch.
Re: NeverSSL
#30example.com works as well. it doesnt redirect to https://example.com