My go-to HTTP-only endpoint is http://example.com . It should be usable for as long as IANA and the Internet as we know it exists.
That supports https too, so current/future browsers will auto-upgrade to https.
RIP HTTP
21–30 of 131 posts
Re: RIP HTTP
#22My go-to HTTP-only endpoint is http://example.com . It should be usable for as long as IANA and the Internet as we know it exists.
Weird, I can only access it on mobile data but not on my wifi.
Re: RIP HTTP
#23Not that I make a habit of correcting other's spelling and grammar, however: ocassionally -> occasionally
Such mistakes annoy me also, and I apply a simple heuristic: If running a spell checker isn't worth your time, reading what you wrote isn't worth my time.
Re: RIP HTTP
#24See neverssl.com. It has been around for a long time and is useful for making sure you see Wifi terms pages.
Not anymore? (This discussion is pretty much a dupe.) https://news.ycombinator.com/item?id=35789730
See the top reply to that comment:
> They're trying to solve the "how do log into this captive portal" problem, and they needed to make this change to handle that typing "neverssl.com" now often evaluates to "https://neverssl.com".
So, yes, it's still useful for WiFi logins. The change in question was specifically for that purpose. https://neverssl.com now redirects to http://neverssl.com so you can log in to WiFi even if your browser thinks it knows better.
Re: RIP HTTP
#25We apparently still need http to detect wifi portals.
Re: RIP HTTP
#26My go-to HTTP-only endpoint is http://example.com . It should be usable for as long as IANA and the Internet as we know it exists.
Re: RIP HTTP
#27My go-to HTTP-only endpoint is http://example.com . It should be usable for as long as IANA and the Internet as we know it exists.
I use neverssl.com
Re: RIP HTTP
#28Earlier quoted context omitted.
Not educated on this, but whats the problem with it?
With HTTP/1.1 you can debug a request via an ASCII telnet session. Not feasible with QUIC. HTTP/1.1 has a beautiful, elegant, simplistic essence; super easy to implement servers and clients from scratch with literally no dependencies beyond string formatting and basic TCP network APIs.
Given most sites still support HTTP/1.0, it's very unlikely we'll see anyone drop http/1.1 for another three decades, at least. Especially when you factor in how slow some large chunks of the world are to upgrade their OSes and software suites.
Re: RIP HTTP
#29Earlier quoted context omitted.
captive.apple.com does the same trick with a smaller payload.
Where can I go that has a bigger payload? When I've successfully opened a site on an unfamiliar WiFi network I'd like to know up front if I'm gonna have trouble loading stuff.
captive.apple.com is just for captive portals - technically networks can (and do) spoof it, but it's just a connectivity check. Past that you can do any test you want over https.
Re: RIP HTTP
#30Seems a little dramatic...
HTTP isn't going anywhere. HTTPS is literally just HTTP with a TLS layer on top.