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
Increasing the value might increase the risk of Denial of service (DoS) attacks.
Under what conditions does or doesn't it increase the risk of Denial of Service (DoS) attacks? Is this risk mitigated at all by using an AuthenticationScheme on the SignalR hub requiring bearer access tokens in the HTTP headers (i.e. does this prevent unauthorized users from performing DoS attacks)? Are there other implications (security, performance, etc) of increasing the value or disabling the limit entirely?
Description
This page says that
Under what conditions does or doesn't it increase the risk of Denial of Service (DoS) attacks? Is this risk mitigated at all by using an AuthenticationScheme on the SignalR hub requiring bearer access tokens in the HTTP headers (i.e. does this prevent unauthorized users from performing DoS attacks)? Are there other implications (security, performance, etc) of increasing the value or disabling the limit entirely?
See also my SO question about this here.
Page URL
https://learn.microsoft.com/en-us/aspnet/core/signalr/configuration?view=aspnetcore-8.0&tabs=dotnet#configure-server-options
Content source URL
https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/signalr/configuration.md
Document ID
66d252c3-6300-7e28-9aa0-ef2ff66e7a76
Article author
@bradygaster
The text was updated successfully, but these errors were encountered: