Skip to content

Commit 6d978e2

Browse files
committed
Fix typo: continueing -> continuing
1 parent e080fd2 commit 6d978e2

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/application-gateway/for-containers/websockets.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ The WebSocket protocol has several benefits over traditional HTTP requests, incl
2828

2929
To establish a WebSocket connection, a specific HTTP-based handshake is exchanged between the client and the server. If successful, the application-layer protocol is "upgraded" from HTTP to WebSockets, using the previously established TCP connection. Once this occurs, the protocol is changed to WebSockets and traffic no longer flows over HTTP. Data is sent or received using the WebSocket protocol by both endpoints until the WebSocket connection is closed.
3030

31-
![Diagram depicts a client interacting with a web server, connecting with HTTP, upgrading the connection to the WebSocket protocol, and continueing communication over the WebSocket protocol.](./media/websockets/websockets.svg)
31+
![Diagram depicts a client interacting with a web server, connecting with HTTP, upgrading the connection to the WebSocket protocol, and continuing communication over the WebSocket protocol.](./media/websockets/websockets.svg)
3232

3333
> [!NOTE]
3434
> After a connection is upgraded to WebSocket, as an intermediary/terminating proxy, Application Gateway for Containers will send the data received from the frontend to the backend and vice-versa, without any inspection or manipulation capability.

0 commit comments

Comments
 (0)