Fix broken YARP cross-link (#34662)

guardrex · web-flow · commit daad351808bf · 2025-02-06T10:33:01.000-05:00
diff --git a/aspnetcore/blazor/security/blazor-web-app-with-oidc.md b/aspnetcore/blazor/security/blazor-web-app-with-oidc.md
@@ -444,7 +444,7 @@ The following specification is covered:
 * Custom auth state provider services are used by the server and client apps to capture the user's authentication state and flow it between the server and client.
 * This app is a starting point for any OIDC authentication flow. OIDC is configured manually in the app and doesn't rely upon [Microsoft Entra ID](https://www.microsoft.com/security/business/microsoft-entra) or [Microsoft Identity Web](/entra/msal/dotnet/microsoft-identity-web/) packages, nor does the sample app require [Microsoft Azure](https://azure.microsoft.com/) hosting. However, the sample app can be used with Entra, Microsoft Identity Web, and hosted in Azure.
 * Automatic non-interactive token refresh.
-* The [Backend for Frontend (BFF) pattern](/azure/architecture/patterns/backends-for-frontends) is adopted using [.NET Aspire](/dotnet/aspire/get-started/aspire-overview) for service discovery and [YARP](https://microsoft.github.io/reverse-proxy/) for proxying requests to a weather forecast endpoint on the backend app.
+* The [Backend for Frontend (BFF) pattern](/azure/architecture/patterns/backends-for-frontends) is adopted using [.NET Aspire](/dotnet/aspire/get-started/aspire-overview) for service discovery and [YARP](https://dotnet.github.io/yarp/) for proxying requests to a weather forecast endpoint on the backend app.
   * A backend web API uses JWT-bearer authentication to validate JWT tokens saved by the Blazor Web App in the sign-in cookie.
   * Aspire improves the experience of building .NET cloud-native apps. It provides a consistent, opinionated set of tools and patterns for building and running distributed apps.
   * YARP (Yet Another Reverse Proxy) is a library used to create a reverse proxy server.
@@ -482,7 +482,7 @@ The sample app only configures an insecure HTTP launch profile (`http`) for use
 
 ## Server-side Blazor Web App project (`BlazorWebAppOidc`)
 
-The `BlazorWebAppOidc` project is the server-side project of the Blazor Web App. The project uses [YARP](https://microsoft.github.io/reverse-proxy/) to proxy requests to a weather forecast endpoint in the backend web API project (`MinimalApiJwt`) with the `access_token` stored in the authentication cookie.
+The `BlazorWebAppOidc` project is the server-side project of the Blazor Web App. The project uses [YARP](https://dotnet.github.io/yarp/) to proxy requests to a weather forecast endpoint in the backend web API project (`MinimalApiJwt`) with the `access_token` stored in the authentication cookie.
 
 The `BlazorWebAppOidc.http` file can be used for testing the weather data request. Note that the `BlazorWebAppOidc` project must be running to test the endpoint, and the endpoint is hardcoded into the file. For more information, see <xref:test/http-files>.
 
diff --git a/aspnetcore/fundamentals/servers/kestrel/includes/kestrel6.md b/aspnetcore/fundamentals/servers/kestrel/includes/kestrel6.md
@@ -155,7 +155,7 @@ Kestrel can be used by itself or with a *reverse proxy server*. A reverse proxy
 * [Internet Information Services (IIS)](https://www.iis.net/)
 * [Nginx](https://nginx.org)
 * [Apache](https://httpd.apache.org/)
-* [YARP: Yet Another Reverse Proxy](https://microsoft.github.io/reverse-proxy/)
+* [YARP: Yet Another Reverse Proxy](https://dotnet.github.io/yarp/)
 
 Kestrel used as an edge (Internet-facing) web server:
 
diff --git a/aspnetcore/fundamentals/servers/kestrel/when-to-use-a-reverse-proxy.md b/aspnetcore/fundamentals/servers/kestrel/when-to-use-a-reverse-proxy.md
@@ -18,7 +18,7 @@ Kestrel can be used by itself or with a *reverse proxy server*. A reverse proxy
 * [Internet Information Services (IIS)](https://www.iis.net/)
 * [Nginx](https://nginx.org)
 * [Apache](https://httpd.apache.org/)
-* [YARP: Yet Another Reverse Proxy](https://microsoft.github.io/reverse-proxy/)
+* [YARP: Yet Another Reverse Proxy](https://dotnet.github.io/yarp/)
 
 Kestrel used as an edge (Internet-facing) web server:
 
diff --git a/aspnetcore/grpc/performance.md b/aspnetcore/grpc/performance.md
@@ -124,7 +124,7 @@ There are many L7 proxies available. Some options are:
 
 * [Envoy](https://www.envoyproxy.io/) - A popular open source proxy.
 * [Linkerd](https://linkerd.io/) - Service mesh for Kubernetes.
-* [YARP: Yet Another Reverse Proxy](https://microsoft.github.io/reverse-proxy/) - An open source proxy written in .NET.
+* [YARP: Yet Another Reverse Proxy](https://dotnet.github.io/yarp/) - An open source proxy written in .NET.
 
 :::moniker range=">= aspnetcore-5.0"
 
diff --git a/aspnetcore/host-and-deploy/proxy-load-balancer.md b/aspnetcore/host-and-deploy/proxy-load-balancer.md
@@ -243,7 +243,7 @@ To display the logs, add `"Microsoft.AspNetCore.HttpLogging": "Information"` to
 
 * <xref:host-and-deploy/web-farm>
 * [Microsoft Security Advisory CVE-2018-0787: ASP.NET Core Elevation Of Privilege Vulnerability](https://github.com/aspnet/Announcements/issues/295)
-* [YARP: Yet Another Reverse Proxy](https://microsoft.github.io/reverse-proxy/index.html)
+* [YARP: Yet Another Reverse Proxy](https://dotnet.github.io/yarp/)
 
 :::moniker-end
 
@@ -582,6 +582,6 @@ services.Configure<ForwardedHeadersOptions>(options =>
 
 * <xref:host-and-deploy/web-farm>
 * [Microsoft Security Advisory CVE-2018-0787: ASP.NET Core Elevation Of Privilege Vulnerability](https://github.com/aspnet/Announcements/issues/295)
-* [YARP: Yet Another Reverse Proxy](https://microsoft.github.io/reverse-proxy/index.html)
+* [YARP: Yet Another Reverse Proxy](https://dotnet.github.io/yarp/)
 
 :::moniker-end
diff --git a/aspnetcore/migration/inc/abtesting.md b/aspnetcore/migration/inc/abtesting.md
@@ -11,7 +11,7 @@ uid: migration/inc/ab-testing
 
 # A/B Testing endpoints during migration
 
-During incremental migration, new endpoints are brought over to a [YARP](https://microsoft.github.io/reverse-proxy/) enabled ASP.NET Core app. With the default setup, these endpoints are automatically served for all requests once deployed. In order to test these endpoints, or be able to turn them off if needed, additional setup is needed.
+During incremental migration, new endpoints are brought over to a [YARP](https://dotnet.github.io/yarp/) enabled ASP.NET Core app. With the default setup, these endpoints are automatically served for all requests once deployed. In order to test these endpoints, or be able to turn them off if needed, additional setup is needed.
 
 This document describes how to setup a conditional endpoint selection system to enable A/B testing during incremental migration. It assumes a setup as described in [incremental migration overview](xref:migration/inc/overview) as a starting point.
 
diff --git a/aspnetcore/migration/inc/overview.md b/aspnetcore/migration/inc/overview.md
@@ -27,7 +27,7 @@ Before starting the migration, the app targets ASP.NET Framework and runs on Win
 
 ![Before starting the migration](~/migration/inc/overview/static/1.png)
 
-Migration starts by introducing a new app based on ASP.NET Core that becomes the entry point. Incoming requests go to the ASP.NET Core app, which either handles the request or proxies the request to the .NET Framework app via [YARP](https://microsoft.github.io/reverse-proxy/). At first, the majority of code providing responses is in the .NET Framework app, but the ASP.NET Core app is now set up to start migrating routes:
+Migration starts by introducing a new app based on ASP.NET Core that becomes the entry point. Incoming requests go to the ASP.NET Core app, which either handles the request or proxies the request to the .NET Framework app via [YARP](https://dotnet.github.io/yarp/). At first, the majority of code providing responses is in the .NET Framework app, but the ASP.NET Core app is now set up to start migrating routes:
 
 ![start updating routes](~/migration/inc/overview/static/nop.png)
 
diff --git a/aspnetcore/security/authentication/configure-jwt-bearer-authentication.md b/aspnetcore/security/authentication/configure-jwt-bearer-authentication.md
@@ -281,7 +281,7 @@ Some secure token servers encrypt the access tokens. Access tokens do not requir
 
 ## YARP (Yet Another Reverse Proxy)
 
-[YARP (Yet Another Reverse Proxy)](https://microsoft.github.io/reverse-proxy/) is a good tool for handling HTTP requests and forwarding the requests to other APIs. YARP can implement security logic for acquiring new access credentials. YARP is frequently used in the [backend for frontend (BFF)](https://auth0.com/blog/the-backend-for-frontend-pattern-bff/) security architecture. [The Blazor Web App with OIDC documentation](/aspnet/core/blazor/security/blazor-web-app-with-oidc?pivots=with-bff-pattern) demonstrates using YARP to implement the BFF pattern.
+[YARP (Yet Another Reverse Proxy)](https://dotnet.github.io/yarp/) is a good tool for handling HTTP requests and forwarding the requests to other APIs. YARP can implement security logic for acquiring new access credentials. YARP is frequently used in the [backend for frontend (BFF)](https://auth0.com/blog/the-backend-for-frontend-pattern-bff/) security architecture. [The Blazor Web App with OIDC documentation](/aspnet/core/blazor/security/blazor-web-app-with-oidc?pivots=with-bff-pattern) demonstrates using YARP to implement the BFF pattern.
 
 ## Testing APIs
 
