5 ms·
Yeah, the lack of HTTP/2 support has been a long-standing issue with Heroku. They just shipped HTTP/2 terminated at their router [0], and have it on their road
by davepeck 2y ago
Yeah, the lack of HTTP/2 support has been a long-standing issue with Heroku.
They just shipped HTTP/2 terminated at their router [0], and have it on their roadmap [1] to support HTTP/2 all the way through. But it seems like it's at minimum a few months off.
(As for VPC peering: the moment you need that, it sorta feels like Heroku is no longer the right place to be, even ignoring the costs.)
[0] https://blog.heroku.com/heroku-http2-public-beta https://blog.heroku.com/heroku-http2-public-beta
[1] https://github.com/orgs/heroku/projects/130 https://github.com/orgs/heroku/projects/130
- karmelapple 2y agoThey just shipped it, but it's still beta. So... I wouldn't consider that shipped yet.