Hello, I'm looking for best practices related to please Chrome on mass SSL hosting.
let us consider 3 websites a.example.com b.example.com c.example.com they share wildcard *.example.com certificate and they share single IP address. in such case Chrome decides to open a single http2 connection instead of 3 separate connections. while I do not mind to have such optimization, but when 'a.example.com" responds with http2 GOAWAY, that affects also "b.example.com" and " c.example.com". Chrome is not clever enough to open new connections instead of abandoned one. I guess here are people running similar high density SSL hosting, do you have some approaches to please Chrome ? I would be happy if I can tell him to open separate connections for the domains that I wish. Ilya
