Skip to content

Commit 6bb217a

Browse files
authored
Clear description about timeout values
Users cannot understand whether the timeout values are configurable or not. They need clear description that the values are fixed.
1 parent 72dfcf0 commit 6bb217a

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/application-gateway/application-gateway-faq.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,7 @@ For the v2 SKU, open the public IP resource and select **Configuration**. The **
6767

6868
*Keep-Alive timeout* governs how long the Application Gateway will wait for a client to send another HTTP request on a persistent connection before reusing it or closing it. *TCP idle timeout* governs how long a TCP connection is kept open in case of no activity.
6969

70-
The *Keep-Alive timeout* in the Application Gateway v1 SKU is 120 seconds and in the v2 SKU it's 75 seconds. The *TCP idle timeout* is a 4-minute default on the frontend virtual IP (VIP) of both v1 and v2 SKU of Application Gateway.
70+
The *Keep-Alive timeout* in the Application Gateway v1 SKU is 120 seconds and in the v2 SKU it's 75 seconds. The *TCP idle timeout* is a 4-minute default on the frontend virtual IP (VIP) of both v1 and v2 SKU of Application Gateway. These values are fixed, customer can't change them.
7171

7272
### Does the IP or DNS name change over the lifetime of the application gateway?
7373

0 commit comments

Comments
 (0)