<div>
<div class="content wysiwyg-content">
Hi All! 
 
 
I've got a question regarding use of data found within the HubCallerContext. 
 
I notice there's a collection of RequestCookies that hang off of the context. 
They contain the following: 
&nbsp; &nbsp; [0]: {[culture, Microsoft.AspNet.SignalR.Cookie]} 
&nbsp; &nbsp; [1]: {[__RequestVerificationToken_L0VDSQ2, Microsoft.AspNet.SignalR.Cookie]} 
&nbsp; &nbsp; [2]: {[ASP.NET_SessionId, Microsoft.AspNet.SignalR.Cookie]} 
&nbsp; &nbsp; [3]: {[XxxAuth, Microsoft.AspNet.SignalR.Cookie]} 
 
 
In our previous implementation of SignalR, we leveraged the SessionId which hung 
off of the HttpContext Session. Since use of the Session is no longer supported 
in SignalR 2.x, we were forced to look for an alternative. 
 
In doing so, we noticed &quot;ASP.NET_SessionId&quot; in the RequestCookies. 
Does anyone know of any issues or restrictions with using it? 
Is this a safe option to utilize? 
 
 
Thoughts? 
 
Thanks, 
JohnB
</div>
</div>

Hi All! 


I've got a question regarding use of data found within the HubCallerContext.

I notice there's a collection of RequestCookies that hang off of the context.
They contain the following:
    [0]: {[culture, Microsoft.AspNet.SignalR.Cookie]}
    [1]: {[__RequestVerificationToken_L0VDSQ2, Microsoft.AspNet.SignalR.Cookie]}
    [2]: {[ASP.NET_SessionId, Microsoft.AspNet.SignalR.Cookie]}
    [3]: {[XxxAuth, Microsoft.AspNet.SignalR.Cookie]}


In our previous implementation of SignalR, we leveraged the SessionId which hung
off of the HttpContext Session. Since use of the Session is no longer supported
in SignalR 2.x, we were forced to look for an alternative. 

In doing so, we noticed "ASP.NET_SessionId" in the RequestCookies.
Does anyone know of any issues or restrictions with using it?
Is this a safe option to utilize?


Thoughts?

Thanks,
JohnB

Are there any known issues with using the ASP.net SessionId embedded in the HubCallerContext RequestCookies in SignalR 2.x?

The successor to Active Server Pages, ASP.NET websites utilize the .NET framework to produce dynamic, data and content-driven web applications and services. ASP.NET code can be written using any .NET supported language. As of 2009, ASP.NET can also apply the Model-View-Controller (MVC) pattern to web applications

ASP.NET

The .NET Framework is not specific to any one programming language; rather, it includes a library of functions that allows developers to rapidly build applications. Several supported languages include C#, VB.NET, C++ or ASP.NET.

.NET Programming

Asynchronous JavaScript and XML (AJAX) is a group of interrelated Web development techniques used on the client-side to create asynchronous Web applications. With AJAX, web applications can send data to and retrieve from a server asynchronously (in the background) without interfering with the display and behavior of the existing page. HTML and CSS can be used in combination to mark up and style information. The Document Object Model (DOM) is accessed with JavaScript to dynamically display and allow interaction with the information presented.