fix broken links (#30890)

dotnet · Oct 31, 2023 · 27027e5 · 27027e5
1 parent 126e004
commit 27027e5
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/aspnetcore/fundamentals/servers/httpsys/includes/httpsys5-7.md b/aspnetcore/fundamentals/servers/httpsys/includes/httpsys5-7.md
@@ -50,7 +50,7 @@ HTTP/2 is enabled by default. If an HTTP/2 connection isn't established, the con
 
 ## HTTP/3 support
 
-[HTTP/3](https://quicwg.org/base-drafts/v2-samples/draft-ietf-quic-http.html) is enabled for ASP.NET Core apps when the following base requirements are met:
+[HTTP/3](https://datatracker.ietf.org/doc/rfc9114/) is enabled for ASP.NET Core apps when the following base requirements are met:
 
 * Windows Server 2022/Windows 11 or later
 * An `https` url binding is used.

diff --git a/aspnetcore/fundamentals/servers/kestrel/includes/http3-6-7.md b/aspnetcore/fundamentals/servers/kestrel/includes/http3-6-7.md
@@ -70,7 +70,7 @@ HTTP/3 and QUIC have a number of benefits compared to HTTP/1.1 and HTTP/2:
 
 :::moniker range="= aspnetcore-6.0"
 
-[HTTP/3](https://quicwg.org/base-drafts/v2-samples/draft-ietf-quic-http.html) is the third and upcoming major version of HTTP. This article discusses requirements for HTTP/3 and how to configure Kestrel to use it.
+[HTTP/3](https://datatracker.ietf.org/doc/rfc9114/) 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.