Session isn't supported in SignalR apps because a SignalR Hub may execute independent of an HTTP context. Critical application data should be stored in the user database and cached in session only as a performance optimization. The site should continue to function without the session data. The session data is backed by a cache and considered ephemeral data. Session state uses a store maintained by the app to persist data across requests from a client. Session state is an ASP.NET Core scenario for storage of user data while the user browses a web app. For more information, see General Data Protection Regulation (GDPR) support in ASP.NET Core. See the European Union General Data Protection Regulations (GDPR) when issuing cookies and dealing with privacy concerns.
The cookie can be used to access the user's personalized settings, such as their preferred website background color. The cookie can store the user's name, account name, or unique user ID such as a GUID. The user is only identified and not authenticated in most cases. However, cookies are generally the most durable form of data persistence on the client.Ĭookies are often used for personalization, where content is customized for a known user. Cookies can be deleted by users and expire on clients. Only a limited number of cookies are available for each domain.īecause cookies are subject to tampering, they must be validated by the app. Most browsers restrict cookie size to 4096 bytes. Ideally, only an identifier should be stored in a cookie with the data stored by the app. Because cookies are sent with every request, their size should be kept to a minimum. CookiesĬookies store data across requests. For more information and alternative state management approaches for Blazor Server apps, see ASP.NET Core Blazor state management. SignalR apps can store per-connection state in Context.Items in the hub. SignalR apps shouldn't use session state and other state management approaches that rely upon a stable HTTP context to store information. SignalR/Blazor Server and HTTP context-based state management May include data stored using server-side app code.
Each approach is described later in this article. State can be stored using several approaches. This article describes several approaches to preserve user data between requests.
By default, HTTP requests are independent messages that don't retain user values. By Rick Anderson, Kirk Larkin, and Diana LaRose
0 kommentar(er)
