You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: xml/System.Net.Http/HttpClientHandler.xml
+8-5Lines changed: 8 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -30,13 +30,16 @@
30
30
<formattype="text/markdown"><![CDATA[
31
31
32
32
## Remarks
33
-
The `HttpClientHandler` class and classes derived from it enable developers to configure a variety of options ranging from proxies to authentication.
33
+
34
+
The `HttpClientHandler` class and classes derived from it enable developers to configure a variety of options ranging from proxies to authentication.
34
35
35
36
### HttpClientHandler in .NET Core
36
37
37
-
Starting with .NET Core 2.1, the <xref:System.Net.Http.SocketsHttpHandler?displayProperty=nameWithType> class instead of `HttpClientHandler` provides the implementation used by higher-level HTTP networking APIs. You can configure your application to use `HttpClientHandler` instead in any of the following ways:
38
+
Starting in .NET Core 2.1, the implementation of the `HttpClientHandler` class was changed to be based on the cross-platform HTTP protocol stack used by the <xref:System.Net.Http.SocketsHttpHandler?displayProperty=nameWithType> class. Prior to .NET Core 2.1, the `HttpClientHandler` class used older HTTP protocol stacks (<xref:System.Net.Http.WinHttpHandler> on Windows and `CurlHandler`, an internal class implemented on top of Linux's native libcurl component, on Linux).
39
+
40
+
You can configure your app to use the older HTTP protocol stacks in one of the following three ways:
38
41
39
-
- By calling the <xref:System.AppContext.SetSwitch%2A?displayProperty=nameWithType> method as follows:
42
+
- Call the <xref:System.AppContext.SetSwitch%2A?displayProperty=nameWithType> method:
0 commit comments