We welcome user feedback and feature requests!

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.

2,986 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Martin Suchan shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    Hi all. As everyone had noticed, we have upgraded App Service resources to Server 2016. As mentioned in our updates, this is indeed paving the way to HTTP/2 support across the board. As we are settling in with stability of the new OS version, we will begin work to open up HTTP/2. When I have a concrete timeline to share, I will do so. We should expect that in the next few months.

    Thanks,
    Oded

    102 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • Embers commented  ·   ·  Flag as inappropriate

        2 years too late to the party. MS seem oblivious that taking so long rolling out key features or even their own OS and Frameworks so slowly to Azure is a problem, damaging their credibility and uptake. As always it is bread and butter functionality / use cases which are missing from Azure. Http2 still needs to be rolled out to App Gateway and WAF. The need to use an ASE just to put a website in a VNET to run it securely and the ridiculous cost (£1000+ per month) to run the ASE is another example of 'old mind set MS' slipping back in.

      • Nik commented  ·   ·  Flag as inappropriate

        When will HTTP/2 be turned on for App Services how we are finally on 10.0.14393?

      • Nik commented  ·   ·  Flag as inappropriate

        My UK South boxes are on 10.0.14393 now... :-D

        Windows Server 2016 was released to manufacturing on 26 September 2016, bearing the version number of 10.0.14393

      • Mike commented  ·   ·  Flag as inappropriate

        From my understanding, it requires additional setup that MS has to do, i.e. there is nothing you can do in the portal (that I know of). The Windows 2016 update is a like a first step requirement before they can enable HTTP2. My guess is they are going to complete the 2016 upgrades, then give it a couple of months to make sure no issues from that come up. Hopefully they'll be testing the HTTP2 configurations simultaneously so they can roll it out quicker once they're sure the upgrades are stable. I think the reason they haven't announced any timeframe is they're just concerned about any unknowns that could come up and might take time to work through.

      • NIkola Biondic commented  ·   ·  Flag as inappropriate

        Hi guys, I can see in the portal that my web sites are now running on Windows Server 2016, but requests are still being made through http1.1 even though I have https. Does it require any additional setting up?

      • Mike commented  ·   ·  Flag as inappropriate

        I did notice it was done on my servers in EASTUS2, sometime within the past week or so. You can see this in your azure portal under 'overview'. My guess is that Microsoft is taking this upgrade region by region, so the date could vary, and I recall a communication from them that said it would be complete systemwide sometime in January.

      • Anonymous commented  ·   ·  Flag as inappropriate

        Hello, was the update of App service infra to service 2016 done? If yes, on which date?

      • Paras commented  ·   ·  Flag as inappropriate

        As per recent communications :

        Host OS update will begin on Monday, December 4, 2017, and continue through January 2018

        this update will move the App Service and Functions infrastructure to Windows Server 2016. This update paves the way to allow the HTTP/2 protocol for App Service and Functions.

      • Ad G commented  ·   ·  Flag as inappropriate

        Microsoft apparently has started working on this, but refused to give any ETA for http2.

      • Constantin Radulescu commented  ·   ·  Flag as inappropriate

        This change created an outage for our production. We are using SSL and because your configuration dose send "Upgrade " answer into the header the application failed, cause they trying to make an http2 connection over a SSL connection and the h2 frame is NULL. For the ppl that has applications that are affected by this issue, the only solution I could find is to migrate the services on North Europe temporary until I will replace the azure app webservices with a personal solution, so the services wont be affected anymore about this kind of changes. To pass services from http1.1 to http2 should be optionally and not mandatory. I am aware http2 is was better then http 1.1 but you need to take in consideration that we have services on production that are serving millions of requests and we cant migrate so easily this kind of services.

      ← Previous 1 3 4 5 6

      Feedback and Knowledge Base