Training
Module
Implement HTTP operations in ASP.NET Razor Pages - Training
Implement HTTP operations in ASP.NET Razor Pages
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Note
This isn't the latest version of this article. For the current release, see the .NET 9 version of this article.
Warning
This version of ASP.NET Core is no longer supported. For more information, see the .NET and .NET Core Support Policy. For the current release, see the .NET 9 version of this article.
Important
This information relates to a pre-release product that may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
For the current release, see the .NET 9 version of this article.
HTTP/3 is an approved standard and the third major version of HTTP. This article discusses the requirements for HTTP/3. HTTP/3 is fully supported in ASP.NET Core 7.0 and later.
Important
Apps configured to take advantage of HTTP/3 should be designed to also support HTTP/1.1 and HTTP/2.
HTTP/3 has different requirements depending on the operating system. If the platform that Kestrel is running on doesn't have all the requirements for HTTP/3, then it's disabled, and Kestrel will fall back to other HTTP protocols.
libmsquic
package installed.libmsquic
is published via Microsoft's official Linux package repository at packages.microsoft.com
. To install this package:
packages.microsoft.com
repository. See Linux Software Repository for Microsoft Products for instructions.libmsquic
package using the distro's package manager. For example, apt install libmsquic=1.9*
on Ubuntu.Note: .NET 6 is only compatible with the 1.9.x versions of libmsquic. Libmsquic 2.x is not compatible due to breaking changes. Libmsquic receives updates to 1.9.x when needed to incorporate security fixes.
HTTP/3 isn't currently supported on macOS and may be available in a future release.
HTTP/3 is not enabled by default. Add configuration to Program.cs
to enable HTTP/3.
var builder = WebApplication.CreateBuilder(args);
builder.WebHost.ConfigureKestrel((context, options) =>
{
options.ListenAnyIP(5001, listenOptions =>
{
listenOptions.Protocols = HttpProtocols.Http1AndHttp2AndHttp3;
listenOptions.UseHttps();
});
});
The preceding code configures port 5001 to:
HttpProtocols.Http1AndHttp2AndHttp3
.UseHttps
. HTTP/3 requires HTTPS.Because not all routers, firewalls, and proxies properly support HTTP/3, HTTP/3 should be configured together with HTTP/1.1 and HTTP/2. This can be done by specifying HttpProtocols.Http1AndHttp2AndHttp3
as an endpoint's supported protocols.
For more information, see Configure endpoints for the ASP.NET Core Kestrel web server.
HTTP/3 is discovered as an upgrade from HTTP/1.1 or HTTP/2 via the alt-svc
header. That means the first request will normally use HTTP/1.1 or HTTP/2 before switching to HTTP/3. Kestrel automatically adds the alt-svc
header if HTTP/3 is enabled.
Browsers don't allow self-signed certificates on HTTP/3, such as the Kestrel development certificate.
HttpClient
can be used for localhost/loopback testing in .NET 6 or later. Extra configuration is required when using HttpClient
to make an HTTP/3 request:
HttpRequestMessage.Version
to 3.0, orHttpRequestMessage.VersionPolicy
to HttpVersionPolicy.RequestVersionOrHigher
.HTTP/3 uses the same semantics as HTTP/1.1 and HTTP/2: the same request methods, status codes, and message fields apply to all versions. The differences are in the underlying transport. Both HTTP/1.1 and HTTP/2 use TCP as their transport. HTTP/3 uses a new transport technology developed alongside HTTP/3 called QUIC.
HTTP/3 and QUIC have a number of benefits compared to HTTP/1.1 and HTTP/2:
HTTP/3 is a proposed standard and the third major version of HTTP. This article discusses requirements for HTTP/3. HTTP/3 is fully supported in ASP.NET Core 7.0 and later.
Important
Apps configured to take advantage of HTTP/3 should be designed to also support HTTP/1.1 and HTTP/2.
HTTP/3 has different requirements depending on the operating system. If the platform that Kestrel is running on doesn't have all the requirements for HTTP/3 then it's disabled, and Kestrel will fallback to other HTTP protocols.
libmsquic
package installed.libmsquic
is published via Microsoft's official Linux package repository at packages.microsoft.com
. To install this package:
packages.microsoft.com
repository. See Linux Software Repository for Microsoft Products for instructions.libmsquic
package using the distro's package manager. For example, apt install libmsquic=1.9*
on Ubuntu.Note: .NET 6 is only compatible with the 1.9.x versions of libmsquic. Libmsquic 2.x is not compatible due to breaking changes. Libmsquic receives updates to 1.9.x when needed to incorporate security fixes.
HTTP/3 isn't currently supported on macOS and may be available in a future release.
HTTP/3 is not enabled by default. Add configuration to Program.cs
to enable HTTP/3.
var builder = WebApplication.CreateBuilder(args);
builder.WebHost.ConfigureKestrel((context, options) =>
{
options.ListenAnyIP(5001, listenOptions =>
{
listenOptions.Protocols = HttpProtocols.Http1AndHttp2AndHttp3;
listenOptions.UseHttps();
});
});
The preceding code configures port 5001 to:
HttpProtocols.Http1AndHttp2AndHttp3
.UseHttps
. HTTP/3 requires HTTPS.Because not all routers, firewalls, and proxies properly support HTTP/3, HTTP/3 should be configured together with HTTP/1.1 and HTTP/2. This can be done by specifying HttpProtocols.Http1AndHttp2AndHttp3
as an endpoint's supported protocols.
For more information, see Configure endpoints for the ASP.NET Core Kestrel web server.
HTTP/3 is discovered as an upgrade from HTTP/1.1 or HTTP/2 via the alt-svc
header. That means the first request will normally use HTTP/1.1 or HTTP/2 before switching to HTTP/3. Kestrel automatically adds the alt-svc
header if HTTP/3 is enabled.
Browsers don't allow self-signed certificates on HTTP/3 such as the Kestrel development certificate.
HttpClient
can be used for localhost/loopback testing in .NET 6 or later. Extra configuration is required when using HttpClient
to make an HTTP/3 request:
HttpRequestMessage.Version
to 3.0, orHttpRequestMessage.VersionPolicy
to HttpVersionPolicy.RequestVersionOrHigher
.HTTP/3 uses the same semantics as HTTP/1.1 and HTTP/2: the same request methods, status codes, and message fields apply to all versions. The differences are in the underlying transport. Both HTTP/1.1 and HTTP/2 use TCP as their transport. HTTP/3 uses a new transport technology developed alongside HTTP/3 called QUIC.
HTTP/3 and QUIC have a number of benefits compared to HTTP/1.1 and HTTP/2:
HTTP/3 is the third and upcoming major version of HTTP. This article discusses requirements for HTTP/3 and how to configure Kestrel to use it.
Important
HTTP/3 is available in .NET 6 as a preview feature. The HTTP/3 specification isn't finalized and behavioral or performance issues may exist in HTTP/3 with .NET 6.
For more information on preview feature support, see the preview features supported section.
Apps configured to take advantage of HTTP/3 should be designed to also support HTTP/1.1 and HTTP/2. If issues are identified in HTTP/3, we recommend disabling HTTP/3 until the issues are resolved in a future release of ASP.NET Core. Significant issues are reported at the Announcements GitHub repository.
HTTP/3 has different requirements depending on the operating system. If the platform that Kestrel is running on doesn't have all the requirements for HTTP/3 then it's disabled, and Kestrel will fallback to other HTTP protocols.
libmsquic
package installed.libmsquic
is published via Microsoft's official Linux package repository at packages.microsoft.com
. To install this package:
packages.microsoft.com
repository. See Linux Software Repository for Microsoft Products for instructions.libmsquic
package using the distro's package manager. For example, apt install libmsquic=1.9*
on Ubuntu.Note: .NET 6 is only compatible with the 1.9.x versions of libmsquic. Libmsquic 2.x is not compatible due to breaking changes. Libmsquic receives updates to 1.9.x when needed to incorporate security fixes.
HTTP/3 isn't currently supported on macOS and may be available in a future release.
HTTP/3 is not enabled by default. Add configuration to Program.cs
to enable HTTP/3.
var builder = WebApplication.CreateBuilder(args);
builder.WebHost.ConfigureKestrel((context, options) =>
{
options.ListenAnyIP(5001, listenOptions =>
{
listenOptions.Protocols = HttpProtocols.Http1AndHttp2AndHttp3;
listenOptions.UseHttps();
});
});
The preceding code configures port 5001 to:
HttpProtocols.Http1AndHttp2AndHttp3
.UseHttps
. HTTP/3 requires HTTPS.Because not all routers, firewalls, and proxies properly support HTTP/3, HTTP/3 should be configured together with HTTP/1.1 and HTTP/2. This can be done by specifying HttpProtocols.Http1AndHttp2AndHttp3
as an endpoint's supported protocols.
For more information, see Configure endpoints for the ASP.NET Core Kestrel web server.
HTTP/3 is discovered as an upgrade from HTTP/1.1 or HTTP/2 via the alt-svc
header. That means the first request will normally use HTTP/1.1 or HTTP/2 before switching to HTTP/3. Kestrel automatically adds the alt-svc
header if HTTP/3 is enabled.
Browsers don't allow self-signed certificates on HTTP/3 such as the Kestrel development certificate.
HttpClient
can be used for localhost/loopback testing in .NET 6 or later. Extra configuration is required when using HttpClient
to make an HTTP/3 request:
HttpRequestMessage.Version
to 3.0, orHttpRequestMessage.VersionPolicy
to HttpVersionPolicy.RequestVersionOrHigher
.Some HTTPS scenarios are not yet supported for HTTP/3 in Kestrel. When calling Microsoft.AspNetCore.Hosting.ListenOptionsHttpsExtensions.UseHttps
with HttpsConnectionAdapterOptions while using HTTP/3, setting the following options on the HttpsConnectionAdapterOptions is a no-op (it does nothing):
Calling the following implementations of Microsoft.AspNetCore.Hosting.ListenOptionsHttpsExtensions.UseHttps
throw an error when using HTTP/3:
HTTP/3 uses the same semantics as HTTP/1.1 and HTTP/2: the same request methods, status codes, and message fields apply to all versions. The differences are in the underlying transport. Both HTTP/1.1 and HTTP/2 use TCP as their transport. HTTP/3 uses a new transport technology developed alongside HTTP/3 called QUIC.
HTTP/3 and QUIC have a number of benefits compared to HTTP/1.1 and HTTP/2:
ASP.NET Core feedback
ASP.NET Core is an open source project. Select a link to provide feedback:
Training
Module
Implement HTTP operations in ASP.NET Razor Pages - Training
Implement HTTP operations in ASP.NET Razor Pages