News for hackers. Stuff that matters.
Re:HTTP/3: the past, the present, and the future by takeda on Thursday September 26, 2019 @01:43PM (#21083355)
I wish they would target a real issues of http. For example adding a proper session support and getting rid of cookies.
Re:HTTP/3: the past, the present, and the future by romaniv on Thursday September 26, 2019 @02:01PM (#21083554)
Do you seriously expect Google and Cloudflate to make basic web development easier when they are making tons of money by "managing" its complexity for others? It's in their best interest to make hosting your own content or using smaller hosting providers absolute hell. Just like it's in Google's best interest to make browsers so complex that other browser devs just give up and Chrome derivatives become the only choice.

I'm predicting that eventually Google will start deranking HTTP 1.1 websites.

Re:HTTP/3: the past, the present, and the future by IfOnlyYouKnew on Thursday September 26, 2019 @04:14PM (#21085028)
I have no idea how cookies are supposed to having an impact on hosting in Google's cloud vs your own hardware, or why Google would care about people where something like that is in any way significant.
Re:HTTP/3: the past, the present, and the future by gambler on Thursday September 26, 2019 @04:42PM (#21085308)
>I have no idea how cookies are supposed to having an impact on hosting in Google's cloud vs your own hardware

You do not see how lack of built-in authentication increases complexity of implementing your own website as opposed to "outsourcing" stuff to Gmail, Google Docs and so on? You don't see the zillion "sign in with Google" buttons all over the web? You don't see how cookies are abused for tracking, which benefits Google orders of magnitude more than it would a smaller company?

Re:HTTP/3: the past, the present, and the future by y4mi on Friday September 27, 2019 @06:52AM (#21090464)
Do you even know what "sign in with Google" means?

It's in no way easier than adding keycloak authentication for example, which is another (selfhosted) external authentication solution.

Social auth isnt there to make authentication easier for the website owner. He still has to do everything he'd have to do if he didn't use it.

It's there for the users, do they don't need to remember a bazillion passwords

Re:HTTP/3: the past, the present, and the future by tptacek on Friday September 27, 2019 @12:16AM (#21088354)
The reality is that Google is working as hard on getting rid of cookies as any organization on the Internet.
Re:HTTP/3: the past, the present, and the future by gambler on Friday September 27, 2019 @10:01AM (#21092083)
What you're saying:

Google, a multi-billion dollar corporation that owns most of the browser and search market share, a company that dictates the next transport-layer protocol we will use - this company struggles to design a session-handling mechanism that would out-compete an ugly hack that Netscape ductaped to HTTP in mid-90s.

Re:HTTP/3: the past, the present, and the future by tptacek on Friday September 27, 2019 @12:17PM (#21093568)
Correct.
Re:HTTP/3: the past, the present, and the future by rurban on Thursday September 26, 2019 @06:53PM (#21086480)
The whole idea of HTTP and it's huge win over other server protocols was that it moved session support from the server to the client. You are talking nonsense here. cookies were needed for session persistency eventually.
Re:HTTP/3: the past, the present, and the future by beetheking on Thursday September 26, 2019 @04:19PM (#21085065)
Out of curiosity, what benefit would getting rid of cookies have? And what would be a better way to implement a similar feature?
Re:HTTP/3: the past, the present, and the future by takeda on Thursday September 26, 2019 @04:32PM (#21085210)
Better privacy, simplicity etc.

Cookies were a hack to add sessions on top of http.

Re:HTTP/3: the past, the present, and the future by krferriter on Thursday September 26, 2019 @09:52PM (#21087670)
I don't understand how moving to another session system would be a benefit. What kind of thing are you proposing here?
Re:HTTP/3: the past, the present, and the future by takeda on Friday September 27, 2019 @12:20PM (#21093592)
PHK mentioned it[1] when http/2 was being discussed. I pretty much agree with his opinion about it.

[1] https://varnish-cache.org/docs/trunk/phk/http20.html#beating...

Re:HTTP/3: the past, the present, and the future by vbezhenar on Thursday September 26, 2019 @04:19PM (#21085064)
how session support is different from cookie?
Re:HTTP/3: the past, the present, and the future by takeda on Thursday September 26, 2019 @04:37PM (#21085254)
Session support is what cookies were supposed to solve, a proper support would make things simpler and not allow to abuse cookies for other things.
Re:HTTP/3: the past, the present, and the future by zeroimpl on Thursday September 26, 2019 @08:03PM (#21087045)
I suppose you'd rather they'd have named the headers "Session-Id" and "Set-Session-Id"?
Re:HTTP/3: the past, the present, and the future by thecopy on Thursday September 26, 2019 @04:56PM (#21085448)
Could upu clarify what you mean with proper support for sessions?
Re:HTTP/3: the past, the present, and the future by takeda on Friday September 27, 2019 @12:19PM (#21093582)
Re:HTTP/3: the past, the present, and the future by lone_haxx0r on Thursday September 26, 2019 @10:01PM (#21087731)
And how would you not allow to abuse this session system? Would you make it more 'transactional' than cookies or what?