News for hackers. Stuff that matters.

A comment on HTTP/3 explained. Parent comment

Re:HTTP/3 explained by dochtman on Tuesday February 05, 2019 @11:20AM (#19086708)
QUIC is developed by an IETF working group where anyone can participate, and there are definitely some productive participants who don't work for Google (or any of the other big companies).
[ Parent | on HN ]
Re:HTTP/3 explained by takeda on Tuesday February 05, 2019 @12:25PM (#19087369)
Like they listened to varnish author about making actually useful changes? For example implementing proper sessions, so cookies could go away.
[ Parent | on HN ]
Re:HTTP/3 explained by dagenix on Tuesday February 05, 2019 @12:57PM (#19087707)
Just because they didn't agree with his suggestion to make major changes to the protocol semantics didn't mean they didn't listen to him.
[ Parent | on HN ]
Re:HTTP/3 explained by JoshTriplett on Wednesday February 06, 2019 @03:39AM (#19093651)
TLS Token Binding provides exactly that.
[ Parent | on HN ]
Re:HTTP/3 explained by takeda on Wednesday February 06, 2019 @01:19PM (#19097953)
Yeah, and who is using it? Why cookies are still there?
[ Parent | on HN ]
Re:HTTP/3 explained by anticensor on Wednesday February 06, 2019 @01:58PM (#19098422)
Cookies can do more than sessions.
[ Parent | on HN ]
Re:HTTP/3 explained by takeda on Sunday February 10, 2019 @03:00PM (#19129649)
Sure they can, but sessions are pretty much the only reason why end users have cookies enabled.
[ Parent | on HN ]
Re:HTTP/3 explained by zzzcpan on Tuesday February 05, 2019 @11:23AM (#19086750)
That's not really true. Independent participants don't have any power to affect any of it.
[ Parent | on HN ]