Skip to content

Commit 84f04cc

Browse files
davidshgewarren
andauthored
Fix defaultCredentialsHandleCacheSize docs (#4383)
* Fix defaultCredentialsHandleCacheSize docs The documentation for the `defaultCredentialsHandleCacheSize` setting is incorrect. * Update xml/System.Net.Configuration/WindowsAuthenticationElement.xml Co-authored-by: Genevieve Warren <[email protected]> * Fix typo Co-authored-by: Genevieve Warren <[email protected]>
1 parent e793088 commit 84f04cc

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

xml/System.Net.Configuration/WindowsAuthenticationElement.xml

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,7 @@
6161
<remarks>
6262
<format type="text/markdown"><![CDATA[
6363
64-
By default, Windows allocates a separate SSPI handle for each <xref:System.Net.HttpWebRequest>. If this behavior impacts performance, you can use the `DefaultCredentialsHandleCacheSize` to use a single cached SSPI credential handle for default network credentials. You can do this by setting this property value to 0. This corresponds to the following configuration setting:
64+
By default, the value of `defaultCredentialsHandleCacheSize` is 0. This causes Windows to allocate a separate SSPI handle for each <xref:System.Net.HttpWebRequest>.
6565
6666
```xml
6767
<system.net>
@@ -71,6 +71,8 @@ By default, Windows allocates a separate SSPI handle for each <xref:System.Net.H
7171
</system.net>
7272
```
7373
74+
If this behavior impacts performance, set <xref:System.Net.Configuration.WindowsAuthenticationElement.DefaultCredentialsHandleCacheSize> to a value greater than 0 to use a single, cached SSPI credential handle for default network credentials. The exact value depends on application requirements. Generally, a value between 50 and 100 works for most high-performant applications.
75+
7476
]]></format>
7577
</remarks>
7678
</Docs>

0 commit comments

Comments
 (0)