Skip to content

Fix defaultCredentialsHandleCacheSize docs #4383

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jun 15, 2020
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -61,7 +61,7 @@
<remarks>
<format type="text/markdown"><![CDATA[

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:
By default, the value of `defaultCredentialsHandleCacheSize` is 0. This causes Windows to allocate a separate SSPI handle for each <xref:System.Net.HttpWebRequest>.

```xml
<system.net>
Expand All @@ -71,6 +71,8 @@ By default, Windows allocates a separate SSPI handle for each <xref:System.Net.H
</system.net>
```

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.

]]></format>
</remarks>
</Docs>
Expand Down