See neverssl.com. It has been around for a long time and is useful for making sure you see Wifi terms pages.
NeverSSL is the way to go - they have a number of cache-busting tricks that I haven't seen on other sites.
RIP HTTP
11–20 of 131 posts
Re: RIP HTTP
#12The real death of HTTP isn't that HTTPS is being forced. That's good and bad but at least you can chose and it's HTTP underneath. The death of HTTP is "HTTP"/3 which is barely related to past HTTP protocols and doesn't even allow a choice. Eventually the megacorp browsers will drop real HTTP/1.1 support from their browsers for QUIC based transport. That will be the death of HTTP.
Not educated on this, but whats the problem with it?
Re: RIP HTTP
#13See 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.)
Re: RIP HTTP
#14The real death of HTTP isn't that HTTPS is being forced. That's good and bad but at least you can chose and it's HTTP underneath. The death of HTTP is "HTTP"/3 which is barely related to past HTTP protocols and doesn't even allow a choice. Eventually the megacorp browsers will drop real HTTP/1.1 support from their browsers for QUIC based transport. That will be the death of HTTP.
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.
Re: RIP HTTP
#15The real death of HTTP isn't that HTTPS is being forced. That's good and bad but at least you can chose and it's HTTP underneath. The death of HTTP is "HTTP"/3 which is barely related to past HTTP protocols and doesn't even allow a choice. Eventually the megacorp browsers will drop real HTTP/1.1 support from their browsers for QUIC based transport. That will be the death of HTTP.
What's interesting about this doomsday scenario is it suggests that a few web browsers dictate the course of the www, not several billion websites.
I'm betting that HTTP outlives me and goes beyond the time period I use the www. So far, so good. HTTP/1.1 pipeliing works better than ever. The www is faster than it's ever been and I can consume more web than ever before. I am generally unable to crash the web browser I use to read HTML. All the software I'm using is generally relatively small and solid.
This is only possible because I use TCP clients, TLS proxies and a text-only browser. If I were using a popular web browser I could not make the above statements. Heck, even the supposedly most advanced browser today will choke/become unreasonably sluggish if I try to open a large HTML file, say 20M or more. Whereas I do not hesitate to open/dump 20M HTML files using the text-only browser.
Anyway, I always thought CurveCP was more impressive than HTTP/2 or HTTP/3, which both came later. It did not take a mega-sized "tech" company to create it, only one focused person. No internet advertising needed. I would be willing to bet Mike whatever or whomever at Google used CurveCP for inspiration in creating HTTP/2 and 3. Google, with its trillions of dollars and hundreds of thousands of employees, still has not come up with its own encryption that is any better than what the CurveCP author originally came up with, which is now part of QUIC and myriad other software: https://ianix.com/pub/curve25519-deployment.html
It is what it is. History.
The localhost proxy I use is configured to send all HTTP requests via TLS so the GET request for http://http.rip was sent to https://http.rip, port 443. It appears to have worked. I guess someone forgot to disable HTTPS.
Re: RIP HTTP
#16The real death of HTTP isn't that HTTPS is being forced. That's good and bad but at least you can chose and it's HTTP underneath. The death of HTTP is "HTTP"/3 which is barely related to past HTTP protocols and doesn't even allow a choice. Eventually the megacorp browsers will drop real HTTP/1.1 support from their browsers for QUIC based transport. That will be the death of HTTP.
What do you mean by "doesn't even allow a choice?" Like there's no option for non-secure? Also I would not be too hasty to expect the death of any widely used protocol. You can still access gopher sites.
Correct, TLS is built into the protocol itself instead of it being HTTP wrapped in a TLS stream.
Re: RIP HTTP
#17Hmm, this website supports https with an expired self-signed cert, but the https request never completes and repeats over and over again.
Re: RIP HTTP
#18The real death of HTTP isn't that HTTPS is being forced. That's good and bad but at least you can chose and it's HTTP underneath. The death of HTTP is "HTTP"/3 which is barely related to past HTTP protocols and doesn't even allow a choice. Eventually the megacorp browsers will drop real HTTP/1.1 support from their browsers for QUIC based transport. That will be the death of HTTP.
What do you mean by "doesn't even allow a choice?" Like there's no option for non-secure? Also I would not be too hasty to expect the death of any widely used protocol. You can still access gopher sites.
> What do you mean by "doesn't even allow a choice?" Like there's no option for non-secure?
Yep. http/2 in browsers does not support plaintext, the same will likely be true for QUIC
>You can still access gopher sites.
Not via vanilla mainstream browsers.
Re: RIP HTTP
#19My 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
#20HTTP belonged to a simpler time, the same way in some communities you don't lock the front door.