Pass the TaskCompletionSource to your background service and have it call TrySetResult when you finish with the WebSocket. If you're using a background service to write data to a WebSocket, make sure you keep the middleware pipeline running. > System.ObjectDisposedException: Cannot write to the response body, the response has completed. If you attempt to send or receive a WebSocket message after the middleware pipeline ends, you may get an exception like the following: (0x80004005): The remote party closed the WebSocket connection without completing the close handshake. When using a WebSocket, you must keep the middleware pipeline running for the duration of the connection. Using var webSocket = await () Ĭ = StatusCodes.Status400BadRequest Ī WebSocket request could come in on any URL, but this sample code only accepts requests for /ws.Ī similar approach can be taken in a controller method: public class WebSocketController : ControllerBase The following example is from later in Program.cs: app.Use(async (context, next) => Somewhere later in the request life cycle (later in Program.cs or in an action method, for example) check if it's a WebSocket request and accept the WebSocket request. KeepAliveInterval = TimeSpan.FromMinutes(2) Var webSocketOptions = new WebSocketOptions For more information, see WebSocket origin restriction in this article. AllowedOrigins - A list of allowed Origin header values for WebSocket requests.KeepAliveInterval - How frequently to send "ping" frames to the client to ensure proxies keep the connection open.The following settings can be configured: See the IIS/IIS Express support section.Īdd the WebSockets middleware in Program.cs: app.UseWebSockets() Windows 8 / Windows Server 2012 or later.Windows 7 / Windows Server 2008 or later.NET provides an alternative to WebSockets. ASP.NET Core SignalR with Blazor WebAssemblyįor some apps, gRPC on.Has no significant performance disadvantage compared to using raw WebSockets in most scenarios.Provides a basic remote procedure call app model.Provides transport fallback for environments where WebSockets isn't available.It uses WebSockets whenever possible.įor most applications, we recommend SignalR rather than raw WebSockets. ( RFC 8441) SignalRĪSP.NET Core SignalR is a library that simplifies adding real-time web functionality to apps. WebSockets were originally designed for HTTP/1.1 but have since been adapted to work over HTTP/2. HTTP/2 WebSockets use CONNECT requests rather than GET, so your own routes and controllers may need updating.įor more information, see Add HTTP/2 WebSockets support for existing controllers in this article.Ĭhrome and Edge have HTTP/2 WebSockets enabled by default, and you can enable it in FireFox on the about:config page with the flag.
0 kommentar(er)
