HTTP/2 comes to Firebase Hosting
Blog post from Firebase
Firebase Hosting has introduced HTTP/2 support for all firebaseapp.com traffic and newly provisioned custom domains, providing performance benefits such as multiplexed requests, compressed headers, efficient binary data transfer, and experimental server push. HTTP/2 is automatically used by compatible browsers, and developers are encouraged to avoid excessive file concatenation and domain sharding, serve a manageable number of cacheable files from one domain, and load nonessential resources on demand. Firebase Hosting’s experimental server push can be configured through Link headers in firebase.json to preload or push critical JavaScript and CSS assets, although developers should avoid pushing cached or unnecessary files because of bandwidth costs. The rollout also moves SSL certificates to Server Name Indication (SNI), requiring some older custom-domain users to update CNAME or A-record DNS settings before receiving HTTP/2 support, with a full migration planned by the end of 2016.
No tracked trend matches for this post yet.
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.