You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/load-balancer/load-balancer-tcp-reset.md
+2-3Lines changed: 2 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -56,13 +56,12 @@ It is important to take into account how the idle timeout values set for differe
56
56
| Public IP (attached to load balancer frontend) | 1 | 4 |
57
57
| Load Balancer Inbound Rule | 2 | N/A |
58
58
| Load Balancer Outbound Rule | N/A | 3 |
59
-
| Inbound NAT Rule | 2 | N/A |
60
59
| NAT Gateway | N/A | 1 |
61
60
62
61
### Inbound
63
62
64
-
- If there is an (inbound) load balancer rule with an idle timeout value set differently than the idle timeout of the frontend IP it references, the load balancer idle timeout will take precedence.
65
-
- If there is an inbound NAT rule with an idle timeout value set differently than the idle timeout of the frontend IP it references, the load balancer idle timeout will take precedence.
63
+
- If there is an (inbound) load balancer rule with an idle timeout value set differently than the idle timeout of the frontend IP it references, the load balancer frontend IP idle timeout will take precedence.
64
+
- If there is an inbound NAT rule with an idle timeout value set differently than the idle timeout of the frontend IP it references, the load balancer frontend IP idle timeout will take precedence.
0 commit comments