[Resilient HTTP apps] Add a paragraph describing Http.Resilience RemoveAllResilienceHandlers method (#45335)

* Documentation for the Http.Resilience RemoveAllResilienceHandlers method

* Fixing the build, resolving pr comments

* Silencing the warning for the experimental API

* PR review fixes

* trying to pass the snippet build

* Include range to the code snippet

* use range instead of ids

* fix articles usage

* Grammar fixes

* Update docs/core/resilience/http-resilience.md

---------

Co-authored-by: David Pine <[email protected]>

Author: rainsxng

docs/core/resilience/http-resilience.md

@@ -37,7 +37,7 @@ To add resilience to an <xref:System.Net.Http.HttpClient>, you chain a call on t
 There are several resilience-centric extensions available. Some are standard, thus employing various industry best practices, and others are more customizable. When adding resilience, you should only add one resilience handler and avoid stacking handlers. If you need to add multiple resilience handlers, you should consider using the `AddResilienceHandler` extension method, which allows you to customize the resilience strategies.
 
 > [!IMPORTANT]
-> All of the examples within this article rely on the <xref:Microsoft.Extensions.DependencyInjection.HttpClientFactoryServiceCollectionExtensions.AddHttpClient%2A> API, from the [Microsoft.Extensions.Http](https://www.nuget.org/packages/Microsoft.Extensions.Http) library, which returns an <xref:Microsoft.Extensions.DependencyInjection.IHttpClientBuilder> instance. The <xref:Microsoft.Extensions.DependencyInjection.IHttpClientBuilder> instance is used to configure the <xref:System.Net.Http.HttpClient> and add the resilience handler.
+> All examples within this article rely on the <xref:Microsoft.Extensions.DependencyInjection.HttpClientFactoryServiceCollectionExtensions.AddHttpClient%2A> API, from the [Microsoft.Extensions.Http](https://www.nuget.org/packages/Microsoft.Extensions.Http) library, which returns an <xref:Microsoft.Extensions.DependencyInjection.IHttpClientBuilder> instance. The <xref:Microsoft.Extensions.DependencyInjection.IHttpClientBuilder> instance is used to configure the <xref:System.Net.Http.HttpClient> and add the resilience handler.
 
 ## Add standard resilience handler
 
@@ -77,6 +77,22 @@ Given that you've created an <xref:Microsoft.Extensions.DependencyInjection.IHtt
 
 The preceding code adds the standard resilience handler to the <xref:System.Net.Http.HttpClient>. Like most resilience APIs, there are overloads that allow you to customize the default options and applied resilience strategies.
 
+## Remove standard resilience handlers
+
+There's a method <xref:Microsoft.Extensions.DependencyInjection.ResilienceHttpClientBuilderExtensions.RemoveAllResilienceHandlers*> which removes all previously registered resilience handlers. It's useful when you need to clear existing resilience handlers to add your custom one.
+The following example demonstrates how to configure a custom <xref:System.Net.Http.HttpClient> using the `AddHttpClient` method, remove all predefined resilience strategies, and replace them with new handlers.
+This approach allows you to clear existing configurations and define new ones according to your specific requirements.
+
+:::code language="csharp" source="snippets/http-resilience/Program.RemoveHandlers.cs" range="11-16":::
+
+The preceding code:
+
+- Creates a <xref:Microsoft.Extensions.DependencyInjection.ServiceCollection> instance.
+- Adds the standard resilience handler to all <xref:System.Net.Http.HttpClient> instances.
+- For the "custom" <xref:System.Net.Http.HttpClient>:
+- Removes all predefined resilience handlers that were previously registered. This is useful when you want to start with a clean state to add your own custom strategies.
+- Adds a `StandardHedgingHandler` to the <xref:System.Net.Http.HttpClient>. You can replace `AddStandardHedgingHandler()` with any strategy that suits your application's needs, such as retry mechanisms, circuit breakers, or other resilience techniques.
+
 ### Standard resilience handler defaults
 
 The default configuration chains five resilience strategies in the following order (from the outermost to the innermost):

docs/core/resilience/snippets/http-resilience/Program.RemoveHandlers.cs

@@ -0,0 +1,19 @@
+using System.Net;
+using Microsoft.Extensions.DependencyInjection;
+using Microsoft.Extensions.Http.Resilience;
+
+internal partial class Program
+{
+    private static void RemoveHandlers()
+    {
+        #pragma warning disable EXTEXP0001
+        var services = new ServiceCollection();
+		// By default, we want all HttpClient instances to include the StandardResilienceHandler.
+        services.ConfigureHttpClientDefaults(builder => builder.AddStandardResilienceHandler());
+        // For a named HttpClient "custom" we want to remove the StandardResilienceHandler and add the StandardHedgingHandler instead.
+		services.AddHttpClient("custom")
+            .RemoveAllResilienceHandlers()
+            .AddStandardHedgingHandler();
+        #pragma warning restore EXTEXP0001
+    }
+}