Reflections:
It seems challenging to track multiple windows of an application within a single browser due to shared resources. For instance, a user can have 10 tabs open in Chrome without the application being aware. However, if the user opens up another tab in a different browser like Internet Explorer, distinct sessions are initiated concurrently, allowing access to session information based on how it is stored.
The Session ID remains consistent when using the same browser but changes when different browsers are utilized. The browser sends this ID upon each page load, ensuring continuous identification.
To test this behavior, one can simply log in to platforms like Facebook or Gmail in one tab and explore opening additional tabs to observe whether re-authentication is necessary.
Demonstration:
In Chrome, accessing the Session ID is straightforward by navigating through F12 -> Resources Tab -> Cookies -> Your App -> Session ID. According to Chrome, the SessionID value is randomly generated by ASP.NET and is stored as a non-expiring session cookie in the browser.
When experimenting with multiple tabs, the ID remains constant; however, switching between browsers results in a change in the ID displayed.
Suggestion:
I recommend delving into understanding Session State further for enhanced comprehension and management of session IDs. :)
Explore this MSDN resource on SessionID for more insight.