Skip to content

Commit 9739170

Browse files
authored
Update http-response-codes.md
Clarifying V1 SKU behaviour if the backend response time exceeds the time-out value that is configured in the Backend Setting.
1 parent b54e225 commit 9739170

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/application-gateway/http-response-codes.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -131,7 +131,7 @@ HTTP 502 errors can have several root causes, for example:
131131
- Invalid or improper configuration of custom health probes.
132132
- Azure Application Gateway's [backend pool isn't configured or empty](application-gateway-troubleshooting-502.md#empty-backendaddresspool).
133133
- None of the VMs or instances in [virtual machine scale set are healthy](application-gateway-troubleshooting-502.md#unhealthy-instances-in-backendaddresspool).
134-
- [Request time-out or connectivity issues](application-gateway-troubleshooting-502.md#request-time-out) with user requests.
134+
- [Request time-out or connectivity issues](application-gateway-troubleshooting-502.md#request-time-out) with user requests-Azure application Gateway V1 SKU sent HTTP 502 errors if the backend response time exceeds the time-out value that is configured in the Backend Setting.
135135

136136
For information about scenarios where 502 errors occur, and how to troubleshoot them, see [Troubleshoot Bad Gateway errors](application-gateway-troubleshooting-502.md).
137137

0 commit comments

Comments
 (0)