Skip to content

Commit 3eed0e7

Browse files
committed
No need to call abort on a websocket we know is null
1 parent 6f4919c commit 3eed0e7

1 file changed

Lines changed: 1 addition & 2 deletions

File tree

Common/Websocket/WebsockBaseController.cs

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -158,7 +158,7 @@ await HttpContext.Response.WriteAsJsonAsync(
158158

159159
// Only send close if the socket is still open, this allows us to close the websocket from inside the logic
160160
// We send close if the client sent a close message though
161-
if (WebSocket.State is WebSocketState.Open or WebSocketState.CloseReceived)
161+
if (WebSocket is { State: WebSocketState.Open or WebSocketState.CloseReceived })
162162
{
163163
await WebSocket.CloseOutputAsync(WebSocketCloseStatus.NormalClosure, "Normal closure",
164164
LinkedToken);
@@ -214,7 +214,6 @@ private async Task Logic()
214214
if (WebSocket == null)
215215
{
216216
Logger.LogWarning("WebSocket is null, aborting");
217-
WebSocket?.Abort();
218217
return;
219218
}
220219

0 commit comments

Comments
 (0)