The best practices of HTTP1 are harmful in a HTTP2 world

Re:The best practices of HTTP1 are harmful in a HTTP2 world by PythonicAlpha on Tuesday March 03, 2015 @06:51PM (#9141639)

Serving from a cookie-less domain, still good?

I understand the points made about sharding and concatenating (and also the limits of the arguments), but the short article just mentions cookie-less domains and then just seem to forget about them. So this practice is still valid? Or is there some feature in HTTP2 that also obsoletes this?

[ Parent | on HN ]

Re:The best practices of HTTP1 are harmful in a HTTP2 world by MichaelGG on Tuesday March 03, 2015 @07:05PM (#9141753)

Another comment says that repeated headers aren't sent in the same connection. Thus that'd eliminate sending cookies except the first time, eh? So using multiple domains might hurt, since you need extra DNS lookups and TCP connections.

[ Parent | on HN ]

Re:The best practices of HTTP1 are harmful in a HTTP2 world by michaelmior on Wednesday March 04, 2015 @12:27AM (#9142845)

This is true although if you're not doing domain sharding and just have your static assets on a single domain, I don't think this is a concern. Certainly the performance benefit of having your assets served by a CDN on a different domain will outweigh the cost of the extra connection. (Assuming your CDN supports HTTP2.)

[ Parent | on HN ]

Re:The best practices of HTTP1 are harmful in a HTTP2 world by PythonicAlpha on Tuesday March 03, 2015 @07:10PM (#9141799)

Thanks, yes, when this is the case, that would eliminate the cookie-less domain reason.

[ Parent | on HN ]