Skip to content

HTTP/3: Handle platforms that don't support HTTP/3 #34517

@JamesNK

Description

@JamesNK

If HTTP/2 is not supported then it is silently not enabled. We should do the same for HTTP/3 if a HTTP/3 endpoint is configured and requirements are not met. For example: Insufficient Windows version, Linux msquic package not installed.

  • If an endpoint is configured with other protocols as well as HTTP/3, e.g. Http1AndHttp2AndHttp3, then don't do HTTP/3 and log. Log level INFO? Http1AndHttp2AndHttp3 will become the default in .NET 7 and we don't want to spam people's logs with WARN on startup.
  • If an endpoint is configured with just HTTP/3 then error.

Include "See https://aka.ms/aspnet/kestrel/http3reqs for details." in log and exception message.

Metadata

Metadata

Assignees

Labels

HTTP3area-networkingIncludes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractions

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions