News for hackers. Stuff that matters.

A comment on The Maturing of QUIC. Parent comment

Re:The Maturing of QUIC by toomim on Monday November 11, 2019 @02:38PM (#21508104)
Probably because HTTP is important! What would you change in 1.2?
[ Parent | on HN ]
Re:The Maturing of QUIC by m_eiman on Monday November 11, 2019 @04:00PM (#21508859)
I would replace cookies with a browser controlled session id, 128 random bits encoded as hex.
[ Parent | on HN ]
Re:The Maturing of QUIC by yeaaaaah on Monday November 11, 2019 @04:17PM (#21509004)
Something like HTTP state tokens? https://mikewest.github.io/http-state-tokens/draft-west-http...
[ Parent | on HN ]
Re:The Maturing of QUIC by m_eiman on Tuesday November 12, 2019 @03:28AM (#21512506)
Yes, something like that!

Except also remove support for old-style cookies, which from a quick scan that spec doesn't do.

[ Parent | on HN ]
Re:The Maturing of QUIC by gambler on Monday November 11, 2019 @08:07PM (#21510570)
Ideally, everything related to sessions and domains. The security model we operate under on the web is completely outdated, which adds a ton of complexity to everything else.

Secondly, I would look into cutting out all the parts of the HTTP protocol normal websites aren't commonly using to reduce the complexity of the implementations.

A lot of things HTTP does are probably better off being move to other protocols altogether.

[ Parent | on HN ]