Skip to content

Update HTTP.sys documentation for HTTP3 #36928

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
BrennanConroy wants to merge 2 commits into
base: main
Choose a base branch
from
+5 −2
Open

Update HTTP.sys documentation for HTTP3 #36928

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1817728
Update HTTP.sys documentation for HTTP3
BrennanConroy Mar 26, 2026
36f5e93
Apply suggestion from @wadepickett
wadepickett Mar 26, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions aspnetcore/fundamentals/servers/httpsys.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ description: Learn about HTTP.sys, a web server for ASP.NET Core on Windows. Bui
monikerRange: '>= aspnetcore-2.1'
ms.author: tdykstra
ms.custom: mvc
ms.date: 01/29/2026
ms.date: 03/26/2026
uid: fundamentals/servers/httpsys
---
# HTTP.sys web server implementation in ASP.NET Core
Expand Down Expand Up @@ -90,7 +90,10 @@ app.Use((context, next) =>

Place the preceding code early in the request pipeline.

Http.Sys also supports sending an AltSvc HTTP/2 protocol message rather than a response header to notify the client that HTTP/3 is available. See the [EnableAltSvc registry key](https://techcommunity.microsoft.com/t5/networking-blog/enabling-http-3-support-on-windows-server-2022/ba-p/2676880). This requires netsh sslcert bindings that use host names rather than IP addresses.
Http.Sys also supports sending an AltSvc HTTP/2 protocol message rather than a response header to notify the client that HTTP/3 is available. See the [EnableAltSvc registry key](https://techcommunity.microsoft.com/t5/networking-blog/enabling-http-3-support-on-windows-server-2022/ba-p/2676880).

> [!NOTE]
> This requires netsh sslcert bindings that use host names rather than IP addresses. Replace `ipport` with `hostnameport` in the `netsh http add sslcert` commands below, as well as changing the IP to the HostName, e.g. www.example.com. There is also a bug where using `hostnameport` fails unless the `certstorename` parameter is used. By default use `certstorename=MY`.
Copy link
Copy Markdown
Contributor

@wadepickett wadepickett Mar 26, 2026 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
> This requires netsh sslcert bindings that use host names rather than IP addresses. Replace `ipport` with `hostnameport` in the `netsh http add sslcert` commands below, as well as changing the IP to the HostName, e.g. www.example.com. There is also a bug where using `hostnameport` fails unless the `certstorename` parameter is used. By default use `certstorename=MY`.
> This requires netsh sslcert bindings that use host names rather than IP addresses. Replace `ipport` with `hostnameport` in the `netsh http add sslcert` commands below, and replace the IP address with the `HostName`, for example, `www.example.com`. There's also a known issue where using `hostnameport` fails unless the `certstorename` parameter is specified. By default, use `certstorename=MY`.

Some very minor items per style guide, missing backticks. @BrennanConroy, Did you mean "host name" or HostName (reserved word/parameter) for this text:
"changing the IP to the HostName"

Copy link
Copy Markdown
Member Author

@BrennanConroy BrennanConroy Mar 26, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think "hostname". https://en.wikipedia.org/wiki/Hostname and from the netsh docs https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/netsh-http#remarks


## Kernel mode authentication with Kerberos

Expand Down
Loading