Live data from Hacker News

RIP HTTP

http.rip

1–10 of 131 posts

Re: RIP HTTP

#2
> But be careful, it could have had ads or malware injected and likely was spied on, by ISPs, governments, hotspots, and other malicious actors. And it also suffers a ranking punishment.

Whoa whoa whoa! That is a lot to unpack right after that pledge. "I know I suck but I pledge to be here for you always!"

This feels like some kind of a personality crisis. Maybe we should take a moment to feel out the pros and cons more gently.

Surely _captive portals_ can't be the only thing going for you, HTTP ol' buddy!

(I mean...surely?)

Re: RIP HTTP

#3
The 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.

Re: RIP HTTP

#5
post #4

See neverssl.com. It has been around for a long time and is useful for making sure you see Wifi terms pages.

captive.apple.com does the same trick with a smaller payload.

Re: RIP HTTP

#7

> But be careful, it could have had ads or malware injected and likely was spied on, by ISPs, governments, hotspots, and other malicious actors. And it also suffers a ranking punishment. Whoa whoa whoa! That is a lot to unpack right after that pledge. "I know I suck but I pledge to be here for you always!" This feels like some kind of a personality crisis. Maybe we should take a moment to feel out the pros and cons m…

I use sites like this a fair bit while developing embedded network code.

Re: RIP HTTP

#8
post #5
post #4

See neverssl.com. It has been around for a long time and is useful for making sure you see Wifi terms pages.

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.

Re: RIP HTTP

#9
post #3

The 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.

Re: RIP HTTP

#10
Good riddance!

That the web's core transport protocol used to lack encryption and authentication is an artifact from a time when nobody thought that the Internet was ever going to be used for anything of real-world value.

HTTP is a dinosaur. The age of the dinosaurs is over. It's slightly cool and quirky that it used to be a thing, but we should all be glad that it isn't anymore.

Post reply on HN