Guardrex patch 4

aspnetcore/blazor/fundamentals/signalr.md

@@ -1452,6 +1452,32 @@ Use a <xref:Microsoft.AspNetCore.Components.Server.Circuits.CircuitHandler> to c
 
 :::moniker-end
 
+:::moniker range=">= aspnetcore-8.0"
+
+## Start the SignalR circuit at a different URL
+
+Prevent automatically starting the app by adding `autostart="false"` to the Blazor `<script>` tag ([location of the Blazor start script](xref:blazor/project-structure#location-of-the-blazor-script)). Establish the circuit URL manually using `Blazor.start`. The following example uses the path `/signalr`:
+
+```diff
+- <script src="_framework/blazor.web.js"></script>
++ <script src="_framework/blazor.web.js" autostart="false"></script>
++ <script>
++   Blazor.start({
++     circuit: {
++       configureSignalR: builder => builder.withUrl("/signalr")
++     },
++   });
++ </script>
+```
+
+Add the following <xref:Microsoft.AspNetCore.Builder.ComponentEndpointRouteBuilderExtensions.MapBlazorHub%2A> call with the `/signalr` path to the middleware processing pipeline in the server app's `Program` file:
+
+```csharp
+app.MapBlazorHub("/signalr");
+```
+
+:::moniker-end
+
 ## `IHttpContextAccessor`/`HttpContext` in Razor components
 
 [!INCLUDE[](~/blazor/security/includes/httpcontext.md)]