When I’m having trouble logging into a Wi-Fi network I just go to 128.1.1.1. Seems to work every time.
I always used my own IP until I got to a portal that didn't work with that. Now I use a subdomain of my site. Then one very smart captive portal "moved permanently"'d that and my browser cached it, as it should, and on the next WiFi it tried to load the old one's captive portal x_x. Not sure what the solution is for that, it would happen with neverssl or any of the alternative domains mentioned here as well. I guess…
NeverSSL
101–110 of 206 posts
Re: NeverSSL
#102Earlier quoted context omitted.
Bandwidth, maybe? That page is 53.8 KB total. $2k does seem high though.
A GB of outbound transfer on AWS costs about 0.09$. If the page is 55KB, that means that a single GB is about 18K page loads, but let's make that 15K page loads due to various overhead. To spend 2000$, you'd need to send about 22TB, which are about 330M page loads.
Re: NeverSSL
#103If you’re using a mainstream OS that automatically detects standard captive portals, the main reason why you’ll need this is for “tiered” captive portals like the ones offered on some airplanes. Those tiered captive portals have unique requirements that conflict with OS behavior: A) By default, they want to offer some limited Internet access, such as accessing a sponsored site (often a shopping site like Amazon) or s…
I'm guessing that the way it works today if you're pointing to a non-standard DNS server like Cloudflare's, is that the portal still just intercepts and modifies those requests anyway.
Re: NeverSSL
#104Re: NeverSSL
#105http://example.com also does this, albeit without the promise of never switching
In both Chrome and Firefox, when I type "example.com" into the URL bar, I go to https://example.com , probably because I've visited the https site before and they remember that. So I do not recommend example.com .
Re: NeverSSL
#106Re: NeverSSL
#107Earlier quoted context omitted.
Bandwidth, maybe? That page is 53.8 KB total. $2k does seem high though.
A GB of outbound transfer on AWS costs about 0.09$. If the page is 55KB, that means that a single GB is about 18K page loads, but let's make that 15K page loads due to various overhead. To spend 2000$, you'd need to send about 22TB, which are about 330M page loads.
That equates to 330M/365d = ~900k loads per day.
> it's now grown to about 6 million hits per day, and that's just the traffic that makes it through to the landing page [0]
So he's paying a discount, even.
Re: NeverSSL
#108"This website is for when you try to open Facebook, Google, Amazon, etc on a wifi network, and nothing happens. Type " http://neverssl.com" into your browser's url bar, and you'll be able to log on." I don't get it. How does browsing to http://neverssl.com help you to log in to other websites?
NeverSSL is a huge frustration reducer, especially as I've been able to just tell less technical able co-workers to just go there.
Re: NeverSSL
#109Every week or so you'd have to visit a non-https site so you'd be reconnected.
Re: NeverSSL
#110http://example.com is my captive portal triggering website go-to. IANA reserved and will be there when I need it forever .
Doesn't work for me, seems to fail to resolve. https://i.ibb.co/KmBk7DB/Screenshot-20191103-002332.png