Open mnns opened 6 years ago
This is definitely something we want to support, but are currently blocked by a larger infrastructure problem in our shared front ends. It's on our list to address, but we can't share any timelines on when this will be available.
Would you say, to your best guess, it would be available in 18 months?
We are planning a huge API migration from ASP.NET/WebAPI/Node/Django to Functions. The thing is, HTTP2 is absolutely crucial for us.
Can you please provide update for this issue?
@sinapis Significant progress has been made on adding HTTP/2 support to App Service, and this is the main infrastructure issue that Chris mentioned above. You can track that support here: https://feedback.azure.com/forums/169385-web-apps/suggestions/9552936-enable-http-2-on-azure-web-apps
Looks like this feature is available now. https://feedback.azure.com/forums/169385-web-apps/suggestions/9552936-enable-http-2-on-azure-web-apps
I just tried it out in my function apps (both dynamic and dedicated) and it seems to work well:
I would encourage other interested users to try this out and give us feedback.
I should note that the announcement, with instructions on how to enable, is here: https://blogs.msdn.microsoft.com/appserviceteam/2018/04/13/announcing-http2-support-in-azure-app-service/
As Functions supposed to be the new web API gateway of Azure, I can't really understand how MSFT decided to leave HTTP2 out, the new exploding standard of the internet.
Please provide timeline/thought about HTTP2. It is actually a feature I have to have before migrating our huge project to Functions.