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
Is your feature request related to a problem? Please describe.
I am trying to better understand how the Azure SignalR service works together with Blazor Server running on top of Azure App Service sitting behind Azure Front Door.
Describe the solution you'd like
I'd like to see a detailed diagram showing the communication flow from the starting point of a user opening the web page, ideally with Azure AD based auth steps as well, while making it clear which components initiates the connections to where.
I know that Azure Front door doesn't support WebSockets this is why Azure SignalR service must be used, which means SignalR can never just connect to the App Service behind front door, right? You see this is really not clear to me :)
Additional context
I've found this slide, but it is not detailed enough for me: signalr-deep-dive like what happens after step 5?
Thank you!!
The text was updated successfully, but these errors were encountered:
This document describes the architecture when using Azure SignalR https://learn.microsoft.com/en-us/azure/azure-signalr/signalr-concept-internals
After step 5, the client establishes a persistent connection with Azure SignalR, and Azure SignalR routes the traffic to your App Server through the established "server connections".
Is your feature request related to a problem? Please describe.
I am trying to better understand how the Azure SignalR service works together with Blazor Server running on top of Azure App Service sitting behind Azure Front Door.
Describe the solution you'd like
I'd like to see a detailed diagram showing the communication flow from the starting point of a user opening the web page, ideally with Azure AD based auth steps as well, while making it clear which components initiates the connections to where.
I know that Azure Front door doesn't support WebSockets this is why Azure SignalR service must be used, which means SignalR can never just connect to the App Service behind front door, right? You see this is really not clear to me :)
Additional context
I've found this slide, but it is not detailed enough for me: signalr-deep-dive like what happens after step 5?
Thank you!!
The text was updated successfully, but these errors were encountered: