4 ms·

The year is 2022 and still no HTTP2 support. https://help.heroku.com/JAOCNZ25/does-heroku-have-plans-to-support-http-2 https://help.heroku.com/JAOCNZ25/does-he

• multiplegeorges 5y ago
  Or automated SSL for wildcard domains. > Supporting wildcard domains is something we'd like to do. Up until March 13, 2018, this was an upstream limitation from Let's Encrypt. ... 2018.
• Beltalowda 5y ago
  The changelog that's linked in there is depressing: only updates for languages/environments and an occasional minor update to the actual platform every few months.
• jacobsenscott 5y ago
  Yes, this is :(, but you should be serving all your static assets through a CDN, which will have http2. I can't think of a scenario where I would want to serve anything other than the dynamic content off the heroku server. I don't think http2 buys you much there. So you should be able to get away with at most 2 requests - one to the heroku server, and one to the cdn.
  • mrkurt 5y ago
    The 2022 answer is actually to bake the CDN into your PaaS. Requiring a whole separate CDN for static assets is complication no one needs in their life.
  • bpicolo 5y ago
    Need http/2 for grpc, which is certainly gaining popularity these days