Enabling HTTP/3 support on Windows Server 2022

Published Aug 24 2021 06:00 AM 7,311 Views

Credit and thanks to Matthew Cox and Daniel Ring for implementation work

 

One of the new features Windows Server 2022 brings is native support for hosting HTTP/3 services. In this post, we will discuss how to enable it and how it can benefit web services.

 

HTTP/3 is a major overhaul of HTTP with performance and security in mind. It uses QUIC as a transport (our HTTP server, http.sys, is using msquic) to gain the benefits of eliminated head of line blocking at the transport layer. This is a significant improvement over HTTP/2 which eliminated head of line blocking only at the HTTP layer with streams that allowed a single HTTP/2 connection to replace a set of HTTP/1.1 connections. HTTP/3 also benefits from many lessons learned in HTTP/2, such as simplifying the protocol by removing prioritization.

 

The HTTP/3 standard is nearly complete; its final publication as an RFC is only waiting on formal process at this point. It is already supported by major browsers which means web services are ready to benefit from deploying it.

 

One thing to note before proceeding: these instructions presume there were no changes made to the list of enabled TLS cipher suites on the Windows Server 2022 installation. If this is not the case, consult RFC9001 (“Using TLS to Secure QUIC”) and ensure there are some cipher suites in common between the server and its expected clients. HTTP/3 is built on QUIC which requires TLS 1.3. Turning off TLS 1.3 or disabling TLS 1.3 cipher suites will result in HTTP/3 deployment failures. See “TLS Cipher Suites in Windows Server 2022” to learn how to add cipher suites and which ones are enabled by default.

 

HTTP/3 support is opt-in on Windows Server 2022 via a registry key named “EnableHttp3” with value 1 at “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\HTTP\Parameters”. Running this command from an elevated prompt will create the key:

 

reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\HTTP\Parameters" /v EnableHttp3 /t REG_DWORD /d 1 /f

 

Once this key is set, either restart the http.sys service or reboot Windows to apply the setting.

 

It is likely the web service will need to advertise it is available over HTTP/3 as well using “Alt-Svc” headers in HTTP/2 responses (though this can also be done using HTTP/2 ALTSVC frames). This allows clients who connect over HTTP/2 to learn the service’s HTTP/3 endpoint and use that going forward. This is done by sending an HTTP/3 ALPN (“Application-layer Protocol Negotiation”) identifier with HTTP/2 responses advertising a specific version of HTTP/3 to use for future requests. Sending the ALTSVC frame  can be done by http.sys. That can be enabled by setting the “EnableAltSvc” registry key with the command below. To apply the setting, restart http.sys or reboot Windows.

 

"HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\HTTP\Parameters" /v EnableAltSvc /t REG_DWORD /d 1 /f

 

If all goes well, the service will start serving content over HTTP/3. To ensure this is happening, use Edge to verify the protocol used to serve the web request. Right click on the page, select “Inspect”, then select the “Network” tab. If only “h2” is being used in the “Protocol” column instead of “h3”, try refreshing the page to ensure the ALPN is being honored (the first request will use HTTP/2 which will then advertise HTTP/3 support to Edge for future requests).

32 Comments
%3CLINGO-SUB%20id%3D%22lingo-sub-2679782%22%20slang%3D%22de-DE%22%3ESubject%3A%20Enabling%20HTTP%2F3%20support%20on%20Windows%20Server%202022%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2679782%22%20slang%3D%22de-DE%22%3E%3CP%3EI%20tried%20this%20on%20a%20freshly%20installed%20instance%2C%20but%20I%20got%20no%20QUIC%20response%2C%20although%20I%20do%20see%20TLS%201.3%20being%20used.%20I%20added%20both%20registry%20keys%20and%20restarted%20the%20server.%20I%20also%20cleared%20the%20browser%20cache%20and%20reloaded%20my%20IIS%20website%20multiple%20times.%20Any%20idea%2C%20how%20to%20troubleshoot%20this%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%2C%20on%20another%20machine%20I%20did%20an%20in-place%20update%20from%202019%20to%202022%20and%20on%20this%20server%20I%20don't%20even%20get%20a%20TLS%201.3%20connection.%20The%20browser%20is%20stuck%20on%201.2.%20Any%20idea%2C%20why%20this%20may%20happen%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2682812%22%20slang%3D%22en-US%22%3ERe%3A%20Enabling%20HTTP%2F3%20support%20on%20Windows%20Server%202022%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2682812%22%20slang%3D%22en-US%22%3E%3CP%3EGreat%20post%20but%20windows%20server%202022%20is%20already%20GA%20how%20odd%20this%20may%20sounds%20it%20has%20went%20silent%20to%20GA.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2676880%22%20slang%3D%22en-US%22%3EEnabling%20HTTP%2F3%20support%20on%20Windows%20Server%202022%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2676880%22%20slang%3D%22en-US%22%3E%3CP%3E%3CEM%3ECredit%20and%20thanks%20to%20Matthew%20Cox%20and%20Daniel%20Ring%20for%20implementation%20work%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EOne%20of%20the%20new%20features%20Windows%20Server%202022%20brings%20is%20native%20support%20for%20hosting%20HTTP%2F3%20services.%20In%20this%20post%2C%20we%20will%20discuss%20how%20to%20enable%20it%20and%20how%20it%20can%20benefit%20web%20services.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHTTP%2F3%20is%20a%20major%20overhaul%20of%20HTTP%20with%20performance%20and%20security%20in%20mind.%20It%20uses%20QUIC%20as%20a%20transport%20(our%20HTTP%20server%2C%20http.sys%2C%20is%20using%20%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fmsquic%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Emsquic%3C%2FA%3E)%20to%20gain%20the%20benefits%20of%20eliminated%20head%20of%20line%20blocking%20at%20the%20transport%20layer.%20This%20is%20a%20significant%20improvement%20over%20HTTP%2F2%20which%20eliminated%20head%20of%20line%20blocking%20only%20at%20the%20HTTP%20layer%20with%20streams%20that%20allowed%20a%20single%20HTTP%2F2%20connection%20to%20replace%20a%20set%20of%20HTTP%2F1.1%20connections.%20HTTP%2F3%20also%20benefits%20from%20many%20lessons%20learned%20in%20HTTP%2F2%2C%20such%20as%20simplifying%20the%20protocol%20by%20removing%20prioritization.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20HTTP%2F3%20standard%20is%20nearly%20complete%3B%20its%20%3CA%20href%3D%22https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-quic-http%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Efinal%20publication%3C%2FA%3E%20as%20an%20RFC%20is%20only%20waiting%20on%20formal%20process%20at%20this%20point.%20It%20is%20already%20supported%20by%20major%20browsers%20which%20means%20web%20services%20are%20ready%20to%20benefit%20from%20deploying%20it.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EOne%20thing%20to%20note%20before%20proceeding%3A%20these%20instructions%20presume%20there%20were%20no%20changes%20made%20to%20the%20list%20of%20enabled%20TLS%20cipher%20suites%20on%20the%20Windows%20Server%202022%20installation.%20If%20this%20is%20not%20the%20case%2C%20consult%20RFC9001%20(%E2%80%9C%3CA%20href%3D%22https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Frfc9001%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3EUsing%20TLS%20to%20Secure%20QUIC%3C%2FA%3E%E2%80%9D)%20and%20ensure%20there%20are%20some%20cipher%20suites%20in%20common%20between%20the%20server%20and%20its%20expected%20clients.%20HTTP%2F3%20is%20built%20on%20QUIC%20which%20requires%20TLS%201.3.%20Turning%20off%20TLS%201.3%20or%20disabling%20TLS%201.3%20cipher%20suites%20will%20result%20in%20HTTP%2F3%20deployment%20failures.%20See%20%E2%80%9C%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fwin32%2Fsecauthn%2Ftls-cipher-suites-in-windows-server-2022%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3ETLS%20Cipher%20Suites%20in%20Windows%20Server%202022%3C%2FA%3E%E2%80%9D%20to%20learn%20how%20to%20add%20cipher%20suites%20and%20which%20ones%20are%20enabled%20by%20default.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHTTP%2F3%20support%20is%20opt-in%20on%20Windows%20Server%202022%20via%20a%20registry%20key%20named%20%E2%80%9CEnableHttp3%E2%80%9D%20with%20value%201%20at%20%E2%80%9CHKEY_LOCAL_MACHINE%5CSYSTEM%5CCurrentControlSet%5Cservices%5CHTTP%5CParameters%E2%80%9D.%20Running%20this%20command%20from%20an%20elevated%20prompt%20will%20create%20the%20key%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CPRE%3Ereg%20add%20%22HKEY_LOCAL_MACHINE%5CSYSTEM%5CCurrentControlSet%5Cservices%5CHTTP%5CParameters%22%20%2Fv%20EnableHttp3%20%2Ft%20REG_DWORD%20%2Fd%201%20%2Ff%3C%2FPRE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EOnce%20this%20key%20is%20set%2C%20either%20restart%20the%20http.sys%20service%20or%20reboot%20Windows%20to%20apply%20the%20setting.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIt%20is%20likely%20the%20web%20service%20will%20need%20to%20advertise%20it%20is%20available%20over%20HTTP%2F3%20as%20well%20using%20%E2%80%9CAlt-Svc%E2%80%9D%20headers%20in%20HTTP%2F2%20responses%20(though%20this%20can%20also%20be%20done%20using%20HTTP%2F2%20ALTSVC%20frames).%20This%20allows%20clients%20who%20connect%20over%20HTTP%2F2%20to%20learn%20the%20service%E2%80%99s%20HTTP%2F3%20endpoint%20and%20use%20that%20going%20forward.%20This%20is%20done%20by%20sending%20an%20HTTP%2F3%20ALPN%20(%E2%80%9CApplication-layer%20Protocol%20Negotiation%E2%80%9D)%20identifier%20with%20HTTP%2F2%20responses%20advertising%20a%20specific%20version%20of%20HTTP%2F3%20to%20use%20for%20future%20requests.%20Sending%20the%20ALTSVC%20frame%20%26nbsp%3Bcan%20be%20done%20by%20http.sys.%20That%20can%20be%20enabled%20by%20setting%20the%20%E2%80%9CEnableAltSvc%E2%80%9D%20registry%20key%20with%20the%20command%20below.%20To%20apply%20the%20setting%2C%20restart%20http.sys%20or%20reboot%20Windows.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CPRE%3E%22HKEY_LOCAL_MACHINE%5CSYSTEM%5CCurrentControlSet%5Cservices%5CHTTP%5CParameters%22%20%2Fv%20EnableAltSvc%20%2Ft%20REG_DWORD%20%2Fd%201%20%2Ff%3C%2FPRE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20all%20goes%20well%2C%20the%20service%20will%20start%20serving%20content%20over%20HTTP%2F3.%20To%20ensure%20this%20is%20happening%2C%20use%20Edge%20to%20verify%20the%20protocol%20used%20to%20serve%20the%20web%20request.%20Right%20click%20on%20the%20page%2C%20select%20%E2%80%9CInspect%E2%80%9D%2C%20then%20select%20the%20%E2%80%9CNetwork%E2%80%9D%20tab.%20If%20only%20%E2%80%9Ch2%E2%80%9D%20is%20being%20used%20in%20the%20%E2%80%9CProtocol%E2%80%9D%20column%20instead%20of%20%E2%80%9Ch3%E2%80%9D%2C%20try%20refreshing%20the%20page%20to%20ensure%20the%20ALPN%20is%20being%20honored%20(the%20first%20request%20will%20use%20HTTP%2F2%20which%20will%20then%20advertise%20HTTP%2F3%20support%20to%20Edge%20for%20future%20requests).%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-2676880%22%20slang%3D%22en-US%22%3E%3CP%3EInstructions%20for%20enabling%20HTTP%2F3%20for%20your%20Windows%20Server-based%20web%20services%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2676880%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Ehttp%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Ehttp%20sys%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Ehttp.sys%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Ehttp3%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWS2022%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2699223%22%20slang%3D%22en-US%22%3ERe%3A%20Enabling%20HTTP%2F3%20support%20on%20Windows%20Server%202022%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2699223%22%20slang%3D%22en-US%22%3E%3CP%3EWill%20Windows%20Server%202022%20support%20HTTP%2F3%2BQUIC%20for%20RRAS%20SSTP%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2694775%22%20slang%3D%22en-US%22%3ERe%3A%20Enabling%20HTTP%2F3%20support%20on%20Windows%20Server%202022%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2694775%22%20slang%3D%22en-US%22%3E%3CP%3EGreat%20article%20and%20jeej%20for%20HTTP%2F3%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20test%20with%20Windows%20Server%202022%20build%2020317%20(per%20GA)%2C%20and%20I%20cannot%20get%20a%20HTTP%2F3%20connection.%20I%20do%20however%20have%20TLS%201.3.%20For%20my%20test%20I%20created%20and%20build%20a%20vanilla%20.NET%205.0%20Web%20App%20(MVC)%20that%20I%20deployed%20into%20an%20application%20folder%20in%20my%20test%20website.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOf%20course%20I%20created%20both%20registry%20values%20mentioned%20and%20rebooted%20the%20server.%3C%2FP%3E%3CP%3EWhat%20could%20be%20wrong%3F%20Is%20it%20only%20in%20the%20GA%20version%3F%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F320389%22%20target%3D%22_blank%22%3E%40tojens%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUpdate%3A%20using%20Windows%20Server%202022%20build%26nbsp%3B10.0.20348%20didn't%20change%20the%20isuse%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2710434%22%20slang%3D%22en-US%22%3ERe%3A%20Enabling%20HTTP%2F3%20support%20on%20Windows%20Server%202022%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2710434%22%20slang%3D%22en-US%22%3E%3CP%3EJust%20did%20a%20test%20to%20see%20if%20IIS10%20on%26nbsp%3B%20W2K22%20with%20these%20registry%20additions%20servers%20up%20pages%20over%20QUIC%20but%20so%20far%2C%20no%20joy.%20Any%20information%2C%20pointers%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2745981%22%20slang%3D%22en-US%22%3ERe%3A%20Enabling%20HTTP%2F3%20support%20on%20Windows%20Server%202022%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2745981%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F320389%22%20target%3D%22_blank%22%3E%40tojens%3C%2FA%3E%3C%2FP%3E%3CP%3EAn%20update%20to%20my%20issue%3A%20it%20may%20very%20well%20be%20that%20my%20edge%20firewalls%20are%20blocking%20443%2FUDP%2C%20I%20just%20verified%20I%20_do_%20have%20HTTP%2F3%20transport%20internally%20in%20my%20network.%20Depending%20on%20your%20configuration%2C%20you%20may%20also%20need%20to%20open%20the%20%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fmsquic%2Fblob%2Fmain%2Fdocs%2FDeployment.md%23firewall%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3EWindows%20firewall%3C%2FA%3E%3A%3C%2FP%3E%3CPRE%3E%3CSPAN%20class%3D%22pl-c1%22%3ENew-NetFirewallRule%3C%2FSPAN%3E%20%3CSPAN%20class%3D%22pl-k%22%3E-%3C%2FSPAN%3EDisplayName%20%3CSPAN%20class%3D%22pl-s%22%3E%3CSPAN%20class%3D%22pl-pds%22%3E%22%3C%2FSPAN%3EAllow%20QUIC%3CSPAN%20class%3D%22pl-pds%22%3E%22%3C%2FSPAN%3E%3C%2FSPAN%3E%20%3CSPAN%20class%3D%22pl-k%22%3E-%3C%2FSPAN%3EDirection%20Inbound%20%3CSPAN%20class%3D%22pl-k%22%3E-%3C%2FSPAN%3EProtocol%20UDP%20%3CSPAN%20class%3D%22pl-k%22%3E-%3C%2FSPAN%3ELocalPort%20%3CSPAN%20class%3D%22pl-c1%22%3E443%3C%2FSPAN%3E%20%3CSPAN%20class%3D%22pl-k%22%3E-%3C%2FSPAN%3EAction%20Allow%20%3CSPAN%20class%3D%22pl-k%22%3E-%3C%2FSPAN%3ELocalOnlyMapping%20%3CSPAN%20class%3D%22pl-c1%22%3E%24true%3C%2FSPAN%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3BNote%3A%20this%20is%20on%20build%26nbsp%3B%3CSPAN%3E20348.%20On%20build%2020317%20HTTP%2F3%20still%20seems%20to%20be%20a%20no%20go.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2746283%22%20slang%3D%22de-DE%22%3ESubject%3A%20Enabling%20HTTP%2F3%20support%20on%20Windows%20Server%202022%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2746283%22%20slang%3D%22de-DE%22%3E%3CP%3EI'm%20also%20running%20on%20build%2020348%2C%20and%20while%20TLS%201.3%20is%20working%20fine%2C%20QUIC%20is%20not.%20And%20I'm%20calling%20my%20service%20from%20the%20same%20machine%2C%20so%20the%20Firewall%20should%20not%20be%20the%20issue%20here.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2748089%22%20slang%3D%22en-US%22%3ERe%3A%20Enabling%20HTTP%2F3%20support%20on%20Windows%20Server%202022%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2748089%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1136378%22%20target%3D%22_blank%22%3E%40HenningKrause%3C%2FA%3EDid%20you%20perform%20an%20in-place%20upgrade%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20think%20I%20have%20found%20the%20issue%3A%20TLS%201.3%20cipher%20suite%20'TLS_CHACHA20_POLY1305_SHA256'%20is%20required%20for%20HTTP%2F3%2C%20but%20not%20available%20in%20Schannel%20after%20an%20in-place%20upgrade.%20It's%20only%20available%20if%20you%20have%20installed%20the%20GA%20build%20directly.%20Or%20at%20least%2C%20so%20it%20seems.%3C%2FP%3E%3COL%3E%3CLI%3Eenable%20TLS_CHACHA20_POLY1305_SHA256%3A%20%60Enable-TlsCipherSuite%20-Name%20TLS_CHACHA20_POLY1305_SHA256%20-Position%200%60%3C%2FLI%3E%3CLI%3Eadd%20registry%20values%20for%20EnableHttp3%20and%20EnableAltSvc%3C%2FLI%3E%3CLI%3Everify%20443%2FUDP%20traffic%20is%20allowed%20on%20the%20server%20and%20in%20your%20network%3C%2FLI%3E%3C%2FOL%3E%3CP%3EThis%20worked%20for%20my%20set%20up%2C%20and%20I%20could%20reproduce%20the%20steps.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2748178%22%20slang%3D%22de-DE%22%3ESubject%3A%20Enabling%20HTTP%2F3%20support%20on%20Windows%20Server%202022%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2748178%22%20slang%3D%22de-DE%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1004516%22%20target%3D%22_blank%22%3E%40JanReilink%3C%2FA%3E%2C%20I%20did%20a%20clean%20install%20of%20Windows.%20And%20TLS%201.3%20is%20working.%20Only%20QUIC%20is%20not.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2748375%22%20slang%3D%22en-US%22%3ERe%3A%20Enabling%20HTTP%2F3%20support%20on%20Windows%20Server%202022%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2748375%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1004516%22%20target%3D%22_blank%22%3E%40JanReilink%3C%2FA%3E%26nbsp%3Bi%20ve%20did%20an%20inplace%20upgrade%20an%20updated%20to%20build%2020384%2C%20added%20the%20mentioned%20cipher%20suite%20and%20reg%20keys.%20There%20is%20no%20QUIC%20and%20TLS%201.3%20is%20still%3A%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22el3c_0-1631610092357.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F310238i7743F8E015F61887%2Fimage-size%2Fmedium%3Fv%3Dv2%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22el3c_0-1631610092357.png%22%20alt%3D%22el3c_0-1631610092357.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERequested%20from%20localhost%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20i%20open%20up%20google.com%2C%20QUIC%20ist%20working%20fine%20without%20using%20CHACHA%20POLY%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22el3c_0-1631610703662.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F310239i539313CC01F437C1%2Fimage-size%2Fmedium%3Fv%3Dv2%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22el3c_0-1631610703662.png%22%20alt%3D%22el3c_0-1631610703662.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2748558%22%20slang%3D%22en-US%22%3ERe%3A%20Enabling%20HTTP%2F3%20support%20on%20Windows%20Server%202022%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2748558%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20a%20server%20that%20was%20Windows%20Server%202019%2C%20upgraded%20to%20pre-views%20of%20Windows%20Server%202022%2C%20and%20now%20at%20RTM%2FGA%20fully%20patched.%20IIS%20does%20work%20over%20QUIC%20(both%20registry%20settings%20applied)%20now%20but%20I%20need%20to%20use%20Firefox%20or%20Chrome%2C%20no%20luck%20with%20Edge%20Chromium.%20QUIC%20enabled%20those%20browsers%20as%20found%20on%20Cloudflare%20%3CA%20href%3D%22https%3A%2F%2Fdevelopers.cloudflare.com%2Fhttp3%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3ECloudflare%20HTTP%2F3%20docs%3C%2FA%3E%3C%2FP%3E%3CP%3EI%20did%20not%20have%20to%20add%20any%20ciphers%20due%20to%20in-place%20upgrades%20or%20so.%26nbsp%3B%20Screenshots%20from%20the%20lab%20are%20below.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUPDATE%3A%20While%20chrome%20seemed%20to%20work%20it%20only%20does%20it%20once%20or%20so%20and%20fails%20back%2C%20so%20no%20consistent%20QUIC%20on%20Chrome%20either.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22QUICwithIISonW2K22.jpg%22%20style%3D%22width%3A%20981px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F310258i64C97FCE19788C0A%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22QUICwithIISonW2K22.jpg%22%20alt%3D%22QUICwithIISonW2K22.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2748622%22%20slang%3D%22en-US%22%3EBetreff%3A%20Enabling%20HTTP%2F3%20support%20on%20Windows%20Server%202022%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2748622%22%20slang%3D%22en-US%22%3E%3CP%3EFireFox%20indeed%20uses%20QUIC.%20But%20neither%20Chrome%20nor%20Edge%20do%2C%20although%20I%20explicitly%20enabled%20QUIC%20via%20the%20flags%20(%3CSPAN%3Eedge%3A%2F%2Fflags%2F%23enable-quic%20or%26nbsp%3Bchrome%3A%2F%2Fflags%2F%23enable-quic).%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2748671%22%20slang%3D%22en-US%22%3ERe%3A%20Enabling%20HTTP%2F3%20support%20on%20Windows%20Server%202022%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2748671%22%20slang%3D%22en-US%22%3E%3CP%3ESame%20here%2C%20only%20FF%20is%20working%20with%20QUIC%20and%20some%20stange%20warnings%20while%20sniffing%20the%20traffic%20with%20wireshark%3A%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22el3c_0-1631615869378.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F310274i4E09604CA6BF450B%2Fimage-size%2Fmedium%3Fv%3Dv2%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22el3c_0-1631615869378.png%22%20alt%3D%22el3c_0-1631615869378.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2748713%22%20slang%3D%22en-US%22%3ERe%3A%20Enabling%20HTTP%2F3%20support%20on%20Windows%20Server%202022%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2748713%22%20slang%3D%22en-US%22%3E%3CP%3EI%20can%20confirm%20Firefox%20uses%20QUIC%20%2F%20HTTP%2F3%2C%20and%20in%20my%20environment%20Chrome%20unfortunately%20doesn't.%20Maybe%20has%20something%20to%20do%20with%20the%20supported%20QUIC%2FHTTP3%20draft%20version%20supported%20by%20both%20Chrome%20and%20MsQuic%3F%20But%20strange%20that%20everyone%20has%20different%20results%20with%20in-place%20upgrades%2C%20browsers%2C%20etc.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20following%20images%20are%20from%20the%20same%20page%20(internal%2C%20test%20-%20hence%20the%20self%20signed%20cert).%20Chrome%20doesn't%20do%20HTTP%2F3%2C%20Firefox%20does%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%223.jpg%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F310281i47AEC76C1A597616%2Fimage-size%2Fmedium%3Fv%3Dv2%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%223.jpg%22%20alt%3D%22Firefox%2C%20HTTP%2F3%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3EFirefox%2C%20HTTP%2F3%3C%2FSPAN%3E%3C%2FSPAN%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%222.jpg%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F310280i0CA472C89C751E38%2Fimage-size%2Fmedium%3Fv%3Dv2%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%222.jpg%22%20alt%3D%22Chrome%2C%20HTTP%2F2%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3EChrome%2C%20HTTP%2F2%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EUpdate%3C%2FSTRONG%3E%3A%20I%20just%20disabled%26nbsp%3B%3CSPAN%3ETLS_CHACHA20_POLY1305_SHA256%2C%20rebooted%20the%20server%2C%20and%20HTTP%2F3%20is%20still%20functioning%20in%20Firefox.%20So%20guess%20that's%20not%20a%20requirement.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2766423%22%20slang%3D%22en-US%22%3ERe%3A%20Enabling%20HTTP%2F3%20support%20on%20Windows%20Server%202022%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2766423%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20found%20why%20TL1.3%20was%20not%20working%20on%20my%20side.%3C%2FP%3E%3CP%3EOn%20my%20servers%20(which%20were%20upgraded%20from%20a%20previous%20version%20to%20Win%202022)%20I%20had%20used%20Nartac.com's%20IISCrypto%20tool%20(%20a%20great%20tool%20by%20the%20way)%20to%20configure%20TLS%2Fcipher%2Fschannel%20settings.%26nbsp%3B%3C%2FP%3E%3CP%3EThen%20I%20had%20set%20the%20template%20settings%20on%20the%20IIScrypto%20tool%20back%20to%20%22Server%20Defaults%22%20.%20Upon%20reboot%20TLS1.3%20started%20to%20work.%20So%20if%20you%20had%20used%20IIScrypto%20simply%20revert%20settings%20to%20defaults%20and%20then%20either%20manually%20disable%20early%2Funwanted%20TLS%2Fciphers%2Fhashes%20or%20wait%20for%20new%20release%20from%20Nartac%20or%20use%20IIS'es%20new%20binding%20feature%20%22Disable%20Legacy%20TLS%22.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22arslanchariyev_1-1632127642045.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F311471i9E21059348F7F5A4%2Fimage-size%2Fmedium%3Fv%3Dv2%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22arslanchariyev_1-1632127642045.png%22%20alt%3D%22arslanchariyev_1-1632127642045.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22arslanchariyev_2-1632127844083.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F311472iC60964846F0185B3%2Fimage-size%2Fmedium%3Fv%3Dv2%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22arslanchariyev_2-1632127844083.png%22%20alt%3D%22arslanchariyev_2-1632127844083.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2769058%22%20slang%3D%22en-US%22%3ERe%3A%20Enabling%20HTTP%2F3%20support%20on%20Windows%20Server%202022%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2769058%22%20slang%3D%22en-US%22%3E%3CP%3EWonderful.%20I'm%20looking%20forward%20to%202022%20coming%20to%20Azure%20App%20Service.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2801566%22%20slang%3D%22en-US%22%3ERe%3A%20Enabling%20HTTP%2F3%20support%20on%20Windows%20Server%202022%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2801566%22%20slang%3D%22en-US%22%3E%3CP%3E%5BPlaying%20with%20QUIC%5D%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fwww.chromium.org%2Fquic%2Fplaying-with-quic%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.chromium.org%2Fquic%2Fplaying-with-quic%3C%2FA%3E%3CBR%20%2F%3ENote%20that%20the%20server's%20certificate%20must%20be%20trusted%20by%20a%20default%20CA%20for%20Chrome%2FChromium%20to%20accept%20it%20for%20QUIC.%3CBR%20%2F%3EIf%20you%20are%20using%20a%20self-signed%20certificate%20or%20a%20certificate%20that%20is%20signed%20by%20a%20custom%20CA%2C%3CBR%20%2F%3Eyou%20need%20to%20use%20the%20--ignore-certificate-errors-spki-list%20command%20line%20flag%20to%20trust%20an%20individual%20certificate%20based%20on%20its%20spki.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2845681%22%20slang%3D%22en-US%22%3ERe%3A%20Enabling%20HTTP%2F3%20support%20on%20Windows%20Server%202022%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2845681%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20been%20using%20QUIC%20on%20a%20number%20of%20Windows%20Server%202022%20web%20servers%20since%20the%20beginning%20of%20September%20and%20they%20have%20all%20suffered%20memory%20leaks%20where%20non-paged%20memory%20will%20suddenly%20use%20all%20available%20memory%20on%20the%20server%20requiring%20the%20server%20to%20be%20rebooted.%20I%20have%20been%20able%20to%20trace%20the%20non-page%20memory%20leak%20to%20msquic.sys%20driver.%3C%2FP%3E%3CP%3E%3CSPAN%3E%3CBR%20%2F%3EIf%20you%20enable%26nbsp%3BQUIC%20for%20your%20websites%20in%20Windows%20Server%202022%20and%20get%20non-pooled%20memory%20leak%20problems%2C%20then%20it%20may%20well%20be%26nbsp%3BQUIC%20causing%20the%20problem.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2846964%22%20slang%3D%22en-US%22%3ERe%3A%20Enabling%20HTTP%2F3%20support%20on%20Windows%20Server%202022%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2846964%22%20slang%3D%22en-US%22%3E%3CP%3EAs%20others%20have%20reported%2C%20I'm%20not%20able%20to%20get%20QUIC%20working%20with%20Windows%20Server%202022%20Build%2020384%20with%20IIS.%3C%2FP%3E%3CP%3EI%20have%20tried%20the%20following%3A%3C%2FP%3E%3COL%3E%3CLI%3Eadded%20registry%20values%20for%20EnableHttp3%20and%20EnableAltSvc%3C%2FLI%3E%3CLI%3Everified%20443%2FUDP%20traffic%20is%20allowed%20on%20the%20server%20and%20in%20the%20network%3C%2FLI%3E%3CLI%3Eoptionally%20enabled%26nbsp%3B%3CSPAN%3ETLS_CHACHA20_POLY1305_SHA256%20(by%20default%20it%20is%20disabled.%20See%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fwin32%2Fsecauthn%2Ftls-cipher-suites-in-windows-server-2022%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fwin32%2Fsecauthn%2Ftls-cipher-suites-in-windows-server-2022%3C%2FA%3E)%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3E%3CSPAN%3Everified%20that%20%5B%20%5D%20Disable%20QUIC%20in%20the%20IIS%20bindings%20is%20not%20enabled.%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3E%3CSPAN%3ETested%20with%20the%20latest%20version%20of%20Firefox%2C%20Edge%20and%20Chrome%20from%20the%20local%20network.%3C%2FSPAN%3E%3C%2FLI%3E%3C%2FOL%3E%3CP%3E%3CSPAN%3EAny%20suggestions%20would%20be%20appreciated.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2848902%22%20slang%3D%22en-US%22%3ERe%3A%20Enabling%20HTTP%2F3%20support%20on%20Windows%20Server%202022%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2848902%22%20slang%3D%22en-US%22%3E%3CP%3EHave%20you%20also%20enabled%20TLS%201.3%3F%20It%20doesn't%20seem%20to%20be%20mentioned%20above%2C%20but%20as%20well%20as%20HTTP3%2C%20TLS%201.3%20needs%20to%20be%20enabled%20as%20it%20is%20disabled%20by%20default.%20You%20can%20use%20the%20following%20registry%20keys%20to%20enable%20TLS%201.3%20in%20Windows%20Server%202022%3B%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3E%5BHKEY_LOCAL_MACHINE%5CSYSTEM%5CCurrentControlSet%5CControl%5CSecurityProviders%5CSCHANNEL%5CProtocols%5CTLS%201.3%5D%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%5BHKEY_LOCAL_MACHINE%5CSYSTEM%5CCurrentControlSet%5CControl%5CSecurityProviders%5CSCHANNEL%5CProtocols%5CTLS%201.3%5CClient%5D%3C%2FP%3E%3CP%3E%22DisabledByDefault%22%3Ddword%3A00000000%3C%2FP%3E%3CP%3E%22Enabled%22%3Ddword%3Affffffff%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%5BHKEY_LOCAL_MACHINE%5CSYSTEM%5CCurrentControlSet%5CControl%5CSecurityProviders%5CSCHANNEL%5CProtocols%5CTLS%201.3%5CServer%5D%3C%2FP%3E%3CP%3E%22DisabledByDefault%22%3Ddword%3A00000000%3C%2FP%3E%3CP%3E%22Enabled%22%3Ddword%3Affffffff%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EAlso%2C%20use%26nbsp%3B%3CSPAN%3ENartac.com's%20IISCrypto%3C%2FSPAN%3E%20to%20make%20sure%20that%20the%20following%20Cypher%20Suites%20are%20enabled%3B%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3ETLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384%3C%2FP%3E%3CP%3ETLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256%3C%2FP%3E%3CP%3ETLS_CHACHA20_POLY1305_SHA256%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2849325%22%20slang%3D%22en-US%22%3ERe%3A%20Enabling%20HTTP%2F3%20support%20on%20Windows%20Server%202022%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2849325%22%20slang%3D%22en-US%22%3E%3CP%3EWith%20or%20without%20those%20TLS%201.3%20reg%20keys%20does%20not%20make%20a%20difference%20for%20me.%20In%20FireFox%20it%20seems%20to%20work%20but%20refreshing%20makes%20it%20fall%20back%20to%20HTTP%2F2%20(opposite%20of%20what%20you'd%20expect).%2C%20Chrome%20and%20Edge%20are%20not%20cooperating.%20It%20would%20be%20nice%20if%20MSFT%20could%20give%20a%20bit%20more%20guidance%20or%20info%20on%20the%20state%20of%20QUIC%20for%20IIS.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2849333%22%20slang%3D%22en-US%22%3ERe%3A%20Enabling%20HTTP%2F3%20support%20on%20Windows%20Server%202022%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2849333%22%20slang%3D%22en-US%22%3E%3CP%3EAre%20you%20sending%20an%20alt-svc%3A%26nbsp%3Bh3%3D%22%3A443%22%3B%20response%20header%20to%20the%20web%20browser%20to%20say%20the%20website%20will%20work%20with%20HTTP3%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%26nbsp%3B%20find%20you%20need%20to%20send%20this%20header%20or%20Chrome%20and%20Firefox%20will%20fail%20by%20default%20use%20HTTP2.%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3EI%20also%20find%20that%20Chrome%20can%20be%20picky%20if%20you%20have%20already%20visited%20the%20website%20to%20change%20to%20HTTP3%20and%20you%20may%20need%20to%20reboot%20your%20computer%20in%20order%20for%20Chrome%20to%20start%20using%20HTTP3%20for%20the%20website.%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%222021-10-15_11-11-13.png%22%20style%3D%22width%3A%20444px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F317625iB0728B38AC309CBD%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%222021-10-15_11-11-13.png%22%20alt%3D%222021-10-15_11-11-13.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Version history
Last update:
‎Aug 26 2021 08:40 AM
Updated by: