Add paragraph that Http1AndHttp2 is not supported without TLS (#13891)
parent
a2e996d318
commit
98f814297e
|
@ -5,7 +5,7 @@ description: Troubleshoot errors when using gRPC on .NET Core.
|
|||
monikerRange: '>= aspnetcore-3.0'
|
||||
ms.author: jamesnk
|
||||
ms.custom: mvc
|
||||
ms.date: 08/12/2019
|
||||
ms.date: 08/17/2019
|
||||
uid: grpc/troubleshoot
|
||||
---
|
||||
# Troubleshoot gRPC on .NET Core
|
||||
|
@ -79,6 +79,8 @@ public static IHostBuilder CreateHostBuilder(string[] args) =>
|
|||
});
|
||||
```
|
||||
|
||||
When an HTTP/2 endpoint is configured without TLS, the endpoint's [ListenOptions.Protocols](xref:fundamentals/servers/kestrel#listenoptionsprotocols) must be set to `HttpProtocols.Http2`. `HttpProtocols.Http1AndHttp2` can't be used because TLS is required to negotiate HTTP/2. Without TLS, all connections to the endpoint default to HTTP/1.1, and gRPC calls fail.
|
||||
|
||||
The gRPC client must also be configured to not use TLS. For more information, see [Call insecure gRPC services with .NET Core client](#call-insecure-grpc-services-with-net-core-client).
|
||||
|
||||
> [!WARNING]
|
||||
|
|
Loading…
Reference in New Issue