3 ms·

If your first-party extra domains are advertised in your SSL cert, then Chrome at least will use the same connection for those assets too. See this: https://bl

If your first-party extra domains are advertised in your SSL cert, then Chrome at least will use the same connection for those assets too. See this: https://blog.cloudflare.com/using-cloudflare-to-mix-domain-sharding-and-spdy/ https://blog.cloudflare.com/using-cloudflare-to-mix-domain-s...

buro9 11y ago
The first party extra domains use a different domain and .tld altogether. A bit like how google.com is for maps and anything users upload go to googleusercontent.com. LFGSS is served from www.lfgss.com and the user assets go via lfgss.microco.sm, and proxied user assets (another level of distrust altogether) are going via sslcache.se . I own all of the domains, and they're on the same CloudFlare acount, but we don't yet offer ways to give users control over which domains get SNI'd together, and this is especially true when the domains are on different CloudFlare plans. That said... it's cool. To reduce everything from 8 domains down to 3 or 4 is a significant enough improvement that I'm happy.