Enable HTTP/2 on Azure Web Apps
IIS 10.0 in Windows 10 already supports HTTP/2, Azure Web Apps should support it as well.
Marking as complete! Full deployment for all multi-tenant resources is now complete. Enabling HTTP/2 is documented in the blog here:
We will have UI support in the Azure Portal in the coming weeks for a simple toggle experience but you can update through the resource explorer right now.
Deployment to App Service Environmentx and national clouds will be coming shortly.
Please reach out over the developer forums for any questions or issues encountered.
Peter S commented
thousands of valuable hours spent on learning, configuring, using, and developing various bundlers could be saved.
Olof Wingren commented
Hi, we are running several large scale Web App's with IoC devices connecting over HTTPS. And we are very eager to see TLS 1.3 beeing supported to be able to trim the data usage.
Can Poyrazoglu commented
I still can't seriously believe HTTP/2 isn't implemented. And it's not even in started status, yet "planned".
Microsoft is a total joke. This is totally unacceptable.
Sean Feldman commented
Thank you for the update. While it's comforting that it's still planned and eventually will be done, lack of transparency and amount of time that it takes doesn't add to the confidence to those that needed it a year+ ago.
Still hopeful to see the status changing to "In Progress" shortly replaced with "Finished".
Thank you for your patience on this work item. Enabling HTTP/2 is dependent on a few other internal engineering changes that have yet to be completed. We don't have a timeline yet since those items are still planned and have yet to be prioritized. We will update here once we have a clearer picture.
Sean Feldman commented
Just to keep things in proportion, this is how this requests stacks up to the other top requests: http://imgur.com/a/RYzef
this is a blocker for many people adopting Web Apps. you should really give it more priority
Added 3 votes, please can we get an update?
Vladimir Knobel commented
Is this a joke?
Narasimhan Sridharan commented
Adding 3 votes to this. I seriously cannot believe that hTTP2 is yet unsupported.
Steve DiStefano commented
Looking for an update from Admin on Planned implementation dates?
Martin Suchan commented
Azure CDN just added support for HTTP/2:
Torsten Fischer commented
Any news (Timeline) forthat??????
Ryan Dowling commented
Joshua Kraft commented
Please implement HTTP/2
Joseph Ficara commented
Currently the Azure App Services appears to be based on server 2012. Versions of Windows prior to Windows 10/2016 have an issue with localization. Specifically BCP-47.
Here is an excerpt from the documentation on localization:
"The CultureInfo class specifies a unique name for each culture, based on RFC 4646. The name is a combination of an ISO 639 two-letter lowercase culture code associated with a language and an ISO 3166 two-letter uppercase subculture code associated with a country or region. In addition, for apps that target .NET Framework 4 or later and are running under Windows 10 or later, culture names that correspond to valid BCP-47 language tags are supported. "
Upgrading the App Services to the later version of the OS will resolve this issue.
I submitted a support ticket Feb 1st to help make sure this was getting attention. I suggest everyone keep pushing tickets and responses to the Azure Product Group so the voice gets louder--and HTTP/2 gets an official timeline.
"After discussion with the product group they did confirm they know these are both important and that these issues are both on their radar. There is no timeline whatsoever however. The information on UserVoice is accurate for HTTP/2."
We should post here more.
any update on this?
Jason Elkin commented
I appreciate that this has a massive impact on infrastructure, but it also has a massive impact in App Design.
We're designing/building/testing apps that may not launch for another year on Azure, but many of us will be doing that on (Microsoft) development machines that already support HTTP/2. We need to know if we should be designing for HTTP/2 very early on in a project, and considering the performance benefits (for us developers and MS) surely we need as many apps taking advantage of it at launch as is possible.
At least a ballpark date would stop me having to revisit this page to check for an update every time I start work on a new app.