Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit e15c924

Browse files
committedMar 12, 2019
Adding how websocket works with AppGW
1 parent a3cec04 commit e15c924

File tree

2 files changed

+10
-2
lines changed

2 files changed

+10
-2
lines changed
 

‎articles/application-gateway/application-gateway-websocket.md

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ms.devlang: na
1313
ms.topic: article
1414
ms.tgt_pltfrm: na
1515
ms.workload: infrastructure-services
16-
ms.date: 05/08/2017
16+
ms.date: 03/11/2019
1717
ms.author: amsriva
1818

1919
---
@@ -25,7 +25,15 @@ WebSocket protocol standardized in [RFC6455](https://tools.ietf.org/html/rfc6455
2525

2626
You can continue using a standard HTTP listener on port 80 or 443 to receive WebSocket traffic. WebSocket traffic is then directed to the WebSocket enabled backend server using the appropriate backend pool as specified in application gateway rules. The backend server must respond to the application gateway probes, which are described in the [health probe overview](application-gateway-probe-overview.md) section. Application gateway health probes are HTTP/HTTPS only. Each backend server must respond to HTTP probes for application gateway to route WebSocket traffic to the server.
2727

28-
## Listener configuration element
28+
It's used in apps that benefit from fast, real-time communication, such as chat, dashboard, and game apps.
29+
30+
## How does WebSocket work
31+
32+
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, HTTP is completely out of the picture; data can be sent or received using the WebSocket protocol by both endpoints, until the WebSocket connection is closed.
33+
34+
![addcert](.\media\application-gateway-websocket\websocket.png)
35+
36+
### Listener configuration element
2937

3038
An existing HTTP listener can be used to support WebSocket traffic. The following is a snippet of an httpListeners element from a sample template file. You would need both HTTP and HTTPS listeners to support WebSocket and secure WebSocket traffic. Similarly you can use the [portal](application-gateway-create-gateway-portal.md) or [PowerShell](application-gateway-create-gateway-arm.md) to create an application gateway with listeners on port 80/443 to support WebSocket traffic.
3139

Loading

0 commit comments

Comments
 (0)
Please sign in to comment.