21–30 of 206 posts
I 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.
I 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.
I don’t know where I found it, but it’s charming!
I 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.
You can argue the merits of this being a good thing or not. But it’s fair to call it a work around.
Why not just alksjdhflkjahdskjfhalskjdhfas.com or something that definitely doesn't exist? Since there's no HSTS on domains that don't exist, it should allow the wifi network to redirect to http://myloginportal/whatever and do its thing so you can access the network.
Why not just alksjdhflkjahdskjfhalskjdhfas.com or something that definitely doesn't exist? Since there's no HSTS on domains that don't exist, it should allow the wifi network to redirect to http://myloginportal/whatever and do its thing so you can access the network.
And for good reason. Once user has finished jumping through whatever hoops captive portal want them to jump, a new connection to the same server is likely to be attempted, and having a fake DNS response cached somewhere in libresolv or browser in the client is not the least bit conductive to that.
My favorite to use is http://perdu.com/ I don’t know where I found it, but it’s charming!
Why not just alksjdhflkjahdskjfhalskjdhfas.com or something that definitely doesn't exist? Since there's no HSTS on domains that don't exist, it should allow the wifi network to redirect to http://myloginportal/whatever and do its thing so you can access the network.
Some captive portals do TCP redirection, but no DNS redirection. And for good reason. Once user has finished jumping through whatever hoops captive portal want them to jump, a new connection to the same server is likely to be attempted, and having a fake DNS response cached somewhere in libresolv or browser in the client is not the least bit conductive to that.