I am currently developing a webpage that utilizes SignalR events to trigger ajax requests to our servers. These requests return a URL with a custom URI scheme that, when accessed, opens up a specific program on the client's device without leaving the main page. This functionality is achieved by using window.location = url; within the success callback of the ajax request.
While this method works seamlessly in other parts of our website where we have implemented it, allowing multiple ajax requests and successful redirection without disrupting the main page, I am facing an issue with the new page I am working on. In this case, SignalR disconnects itself right after the initial redirect. The JavaScript console displays a message indicating the connection interruption, which is normal during page unloading. However, since my scenario involves the calling page not actually being unloaded, this behavior is problematic: The connection to ... was interrupted while the page was loading.
My goal is to find a solution that prevents SignalR from disconnecting upon redirect because this disconnection causes subsequent redirects to fail until SignalR reconnects. Any insights or suggestions on how to address this issue would be greatly appreciated.