Clarification for HTTP/2 support with Kestrel on Windows8.1/Server2012R2 (#9522)

pull/9528/head
John Luo 2018-11-08 14:25:47 -08:00 committed by GitHub
parent 3a509ad664
commit 78ec46c2e7
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 5 additions and 2 deletions

View File

@ -138,7 +138,7 @@ When launching an app from a command prompt in the project's folder, [dotnet run
* [Kestrel](xref:fundamentals/servers/kestrel#http2-support)
* Operating system
* Windows Server 2012 R2/Windows 8.1 or later
* Windows Server 2016/Windows 10 or later†
* Linux with OpenSSL 1.0.2 or later (for example, Ubuntu 16.04 or later)
* HTTP/2 will be supported on macOS in a future release.
* Target framework: .NET Core 2.2 or later
@ -153,6 +153,8 @@ When launching an app from a command prompt in the project's folder, [dotnet run
* Public-facing edge server connections use HTTP/2, but the reverse proxy connection to Kestrel uses HTTP/1.1.
* Target framework: Not applicable to IIS out-of-process deployments.
†Kestrel has limited support for HTTP/2 on Windows Server 2012 R2 and Windows 8.1. Support is limited because the list of supported TLS cipher suites available on these operating systems is limited. A certificate generated using an Elliptic Curve Digital Signature Algorithm (ECDSA) may be required to secure TLS connections.
::: moniker-end
::: moniker range="< aspnetcore-2.2"

View File

@ -48,13 +48,14 @@ Kestrel is supported on all platforms and versions that .NET Core supports.
[HTTP/2](https://httpwg.org/specs/rfc7540.html) is available for ASP.NET Core apps if the following base requirements are met:
* Operating system&dagger;
* Windows Server 2012 R2/Windows 8.1 or later
* Windows Server 2016/Windows 10 or later&Dagger;
* Linux with OpenSSL 1.0.2 or later (for example, Ubuntu 16.04 or later)
* Target framework: .NET Core 2.2 or later
* [Application-Layer Protocol Negotiation (ALPN)](https://tools.ietf.org/html/rfc7301#section-3) connection
* TLS 1.2 or later connection
&dagger;HTTP/2 will be supported on macOS in a future release.
&Dagger;Kestrel has limited support for HTTP/2 on Windows Server 2012 R2 and Windows 8.1. Support is limited because the list of supported TLS cipher suites available on these operating systems is limited. A certificate generated using an Elliptic Curve Digital Signature Algorithm (ECDSA) may be required to secure TLS connections.
If an HTTP/2 connection is established, [HttpRequest.Protocol](xref:Microsoft.AspNetCore.Http.HttpRequest.Protocol*) reports `HTTP/2`.