YARP migration /2

Author: Rick-Anderson

aspnetcore/fundamentals/servers/yarp/authn-authz.md

@@ -49,7 +49,7 @@ Example:
 }
 ```
 
-[Authorization policies](https://docs.microsoft.com/aspnet/core/security/authorization/policies) are an ASP.NET Core concept that the proxy utilizes. The proxy provides the above configuration to specify a policy per route and the rest is handled by existing ASP.NET Core authentication and authorization components.
+[Authorization policies](/aspnet/core/security/authorization/policies) are an ASP.NET Core concept that the proxy utilizes. The proxy provides the above configuration to specify a policy per route and the rest is handled by existing ASP.NET Core authentication and authorization components.
 
 Authorization policies can be configured in the application as follows:
 ```
@@ -69,7 +69,7 @@ app.UseAuthorization();
 app.MapReverseProxy();
 ```
 
-See the [Authentication](https://docs.microsoft.com/aspnet/core/security/authentication/) docs for setting up your preferred kind of authentication.
+See the [Authentication](/aspnet/core/security/authentication/) docs for setting up your preferred kind of authentication.
 
 ### Special values:
 
@@ -105,7 +105,7 @@ These authentication types are often bound to a specific connection. They are no
 
 ### Client Certificates
 
-Client certificates are a TLS feature and are negotiated as part of a connection. See [these docs](https://docs.microsoft.com/aspnet/core/security/authentication/certauth) for additional information. The certificate can be forwarded to the destination server as an HTTP header using the [ClientCert](transforms.md#clientcert) transform.
+Client certificates are a TLS feature and are negotiated as part of a connection. See [these docs](/aspnet/core/security/authentication/certauth) for additional information. The certificate can be forwarded to the destination server as an HTTP header using the [ClientCert](transforms.md#clientcert) transform.
 
 ### Swapping authentication types
 

aspnetcore/fundamentals/servers/yarp/config-files.md

@@ -36,7 +36,7 @@ app.MapReverseProxy();
 
 app.Run();
 ```
-**Note**: For details about middleware ordering see [here](https://docs.microsoft.com/aspnet/core/fundamentals/middleware/#middleware-order).
+**Note**: For details about middleware ordering see [here](/aspnet/core/fundamentals/middleware/#middleware-order).
 
 Configuration can be modified during the load sequence using [Configuration Filters](config-filters.md).
 
@@ -93,7 +93,7 @@ Example:
 The routes section is an unordered collection of route matches and their associated configuration. A route requires at least the following fields:
 - RouteId - a unique name
 - ClusterId - refers to the name of an entry in the clusters section.
-- Match - contains either a Hosts array or a Path pattern string. Path is an ASP.NET Core route template that can be defined as [explained here](https://docs.microsoft.com/aspnet/core/fundamentals/routing#route-templates).
+- Match - contains either a Hosts array or a Path pattern string. Path is an ASP.NET Core route template that can be defined as [explained here](/aspnet/core/fundamentals/routing#route-templates).
 Route matching is based on the most specific routes having highest precedence as described [here]( https://docs.microsoft.com/aspnet/core/fundamentals/routing#url-matching). Explicit ordering can be achieved using the `order` field, with lower values taking higher priority.
 
 [Headers](header-routing.md), [Authorization](authn-authz.md), [CORS](cors.md), and other route based policies can be configured on each route entry. For additional fields see [RouteConfig](xref:Yarp.ReverseProxy.Configuration.RouteConfig).

aspnetcore/fundamentals/servers/yarp/config-filters.md

@@ -1,3 +1,16 @@
+---
+uid: fundamentals/servers/yarp/config-filters
+title: Configuration Filters
+description: Configuration Filters
+author: rick-anderson
+ms.author: riande
+ms.date: 02/06/2025
+ms.topic: article
+content_well_notification: AI-contribution
+ms.prod: aspnet-core
+ai-usage: ai-assisted
+---
+
 # Configuration Filters
 
 ## Introduction

aspnetcore/fundamentals/servers/yarp/config-providers.md

@@ -1,3 +1,15 @@
+---
+uid: fundamentals/servers/yarp/config-providers
+title: Extensibility: Configuration Providers
+description: Extensibility: Configuration Providers
+author: rick-anderson
+ms.author: riande
+ms.date: 02/06/2025
+ms.topic: article
+content_well_notification: AI-contribution
+ai-usage: ai-assisted
+---
+
 # Extensibility: Configuration Providers
 
 ## Introduction
@@ -14,7 +26,7 @@ Configuration can be modified during the load sequence using [Configuration Filt
 The routes section is an unordered collection of named routes. A route contains matches and their associated configuration. A route requires at least the following fields:
 - RouteId - a unique name
 - ClusterId - refers to the name of an entry in the clusters section.
-- Match - contains either a Hosts array or a Path pattern string. Path is an ASP.NET Core route template that can be defined as [explained here](https://docs.microsoft.com/aspnet/core/fundamentals/routing#route-templates).
+- Match - contains either a Hosts array or a Path pattern string. Path is an ASP.NET Core route template that can be defined as [explained here](/aspnet/core/fundamentals/routing#route-templates).
 
 [Headers](header-routing.md), [Authorization](authn-authz.md), [CORS](cors.md), and other route based policies can be configured on each route entry. For additional fields see [RouteConfig](xref:Yarp.ReverseProxy.Configuration.RouteConfig).
 

aspnetcore/fundamentals/servers/yarp/cors.md

@@ -1,3 +1,15 @@
+---
+uid: fundamentals/servers/yarp/cors
+title: Cross-Origin Requests (CORS)
+description: Cross-Origin Requests (CORS)
+author: rick-anderson
+ms.author: riande
+ms.date: 02/06/2025
+ms.topic: article
+content_well_notification: AI-contribution
+ai-usage: ai-assisted
+---
+
 # Cross-Origin Requests (CORS)
 
 ## Introduction
@@ -36,7 +48,7 @@ Example:
 }
 ```
 
-[CORS policies](https://docs.microsoft.com/aspnet/core/security/cors#cors-with-named-policy-and-middleware) are an ASP.NET Core concept that the proxy utilizes. The proxy provides the above configuration to specify a policy per route and the rest is handled by existing ASP.NET Core CORS Middleware.
+[CORS policies](/aspnet/core/security/cors#cors-with-named-policy-and-middleware) are an ASP.NET Core concept that the proxy utilizes. The proxy provides the above configuration to specify a policy per route and the rest is handled by existing ASP.NET Core CORS Middleware.
 
 CORS policies can be configured in the application as follows:
 ```

aspnetcore/fundamentals/servers/yarp/destination-resolvers.md

@@ -1,3 +1,16 @@
+
+---
+uid: fundamentals/servers/yarp/destination-resolvers
+title: Extensibility: Destination Resolvers
+description: Extensibility: Destination Resolvers
+author: rick-anderson
+ms.author: riande
+ms.date: 02/06/2025
+ms.topic: article
+content_well_notification: AI-contribution
+ai-usage: ai-assisted
+---
+
 # Extensibility: Destination Resolvers
 
 ## Introduction

aspnetcore/fundamentals/servers/yarp/diagnosing-yarp-issues.md

@@ -3,7 +3,7 @@
 When using a reverse proxy, there is an additional hop from the client to the proxy, and then from the proxy to destination for things to go wrong. This topic should provide some hints and tips for how to debug and diagnose issues when they occur. It assumes that the proxy is already running, and so does not include problems at startup such as configuration errors.
 
 ## Logging
-The first step to being able to tell what is going on with YARP is to turn on [logging](https://docs.microsoft.com/aspnet/core/fundamentals/logging/#configure-logging). This is a configuration flag so can be changed on the fly. YARP is implemented as a middleware component for ASP.NET Core, so you need to enable logging for both YARP and ASP.NET to get the complete picture of what is going on.
+The first step to being able to tell what is going on with YARP is to turn on [logging](/aspnet/core/fundamentals/logging/#configure-logging). This is a configuration flag so can be changed on the fly. YARP is implemented as a middleware component for ASP.NET Core, so you need to enable logging for both YARP and ASP.NET to get the complete picture of what is going on.
 
 By default ASP.NET will log to the console, and the configuration file can be used to control the level of logging.
 
@@ -170,7 +170,7 @@ Forwarder Telemetry [06:41:00.530] => OnForwarderStage :: Stage: ResponseContent
 Forwarder Telemetry [06:41:03.655] => OnForwarderStop :: Status: 200
 ```
 
-The events for Telemetry are fired as they occur, so you can [fish out the HttpContext](https://docs.microsoft.com/aspnet/core/fundamentals/http-context#use-httpcontext-from-custom-components) and the YARP feature from it:
+The events for Telemetry are fired as they occur, so you can [fish out the HttpContext](/aspnet/core/fundamentals/http-context#use-httpcontext-from-custom-components) and the YARP feature from it:
 
 ``` C#
 services.AddTelemetryConsumer<ForwarderTelemetry>();
@@ -220,7 +220,7 @@ public Task MyCustomProxyStep(HttpContext context, Func<Task> next)
 }
 ```
 
-You can also use [ASP.NET middleware](https://docs.microsoft.com/aspnet/core/fundamentals/middleware/write) within Configure that will enable you to inspect the request before the proxy pipeline.
+You can also use [ASP.NET middleware](/aspnet/core/fundamentals/middleware/write) within Configure that will enable you to inspect the request before the proxy pipeline.
 
 > **Note:** The proxy will stream the response from the destination server back to the client, so the response headers and body are not readily accessible via middleware.
 

aspnetcore/fundamentals/servers/yarp/getting-started.md

@@ -1,5 +1,12 @@
 ---
-uid: getting-started
+uid: fundamentals/servers/yarp/getting-started.md
+description: Getting Started with YARP
+author: rick-anderson
+ms.author: riande
+ms.date: 02/06/2025
+ms.topic: article
+content_well_notification: AI-contribution
+ai-usage: ai-assisted
 title: Getting Started with YARP
 ---
 

aspnetcore/fundamentals/servers/yarp/grpc.md

@@ -8,7 +8,7 @@
 
 gRPC requires HTTP/2 for most scenarios. HTTP/1.1 and HTTP/2 are enabled by default on ASP.NET Core servers (YARP's front end) but they require https (TLS) for HTTP/2 so YARP needs to be listening on a `https://` URL.
 
-HTTP/2 over http (non-TLS) is only supported on Kestrel and requires specific settings.  For details see [here](https://docs.microsoft.com/aspnet/core/grpc/aspnetcore#server-options).
+HTTP/2 over http (non-TLS) is only supported on Kestrel and requires specific settings.  For details see [here](/aspnet/core/grpc/aspnetcore#server-options).
 
 This shows configuring Kestrel to use HTTP/2 over http (non-TLS):
 ```json

aspnetcore/fundamentals/servers/yarp/header-guidelines.md

@@ -57,7 +57,7 @@ The Host header indicates which site on the server the request is intended for.
 
 ### X-Forwarded-*, Forwarded
 
-Because a separate connection is used to communicate with the destination, these request headers can be used to forward information about the original connection like the IP, scheme, port, client certificate, etc.. X-Forwarded-For, X-Forwarded-Proto, X-Forwarded-Host, and X-Forwarded-Prefix are enabled by default. This information is subject to spoofing attacks so any existing headers on the request are removed and replaced by default. The destination app should be careful about how much trust it places in these values. See [transforms](transforms.md#defaults) for configuring these in the proxy. See the [ASP.NET docs](https://docs.microsoft.com/aspnet/core/host-and-deploy/proxy-load-balancer) for configuring the destination app to read these headers.
+Because a separate connection is used to communicate with the destination, these request headers can be used to forward information about the original connection like the IP, scheme, port, client certificate, etc.. X-Forwarded-For, X-Forwarded-Proto, X-Forwarded-Host, and X-Forwarded-Prefix are enabled by default. This information is subject to spoofing attacks so any existing headers on the request are removed and replaced by default. The destination app should be careful about how much trust it places in these values. See [transforms](transforms.md#defaults) for configuring these in the proxy. See the [ASP.NET docs](/aspnet/core/host-and-deploy/proxy-load-balancer) for configuring the destination app to read these headers.
 
 ### X-http-method-override, x-http-method, x-method-override