Skip to content

Commit a423505

Browse files
Update troubleshoot-issues.md
If Roxy times out to an origin, it sends a 504 (gateway timeout). If FDv2 encounters the same problem, it sends a 503 (service unavailable). Changing the documentation accordingly
1 parent fb6e10d commit a423505

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/frontdoor/troubleshoot-issues.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,11 +17,11 @@ This article describes how to troubleshoot common routing problems that you migh
1717

1818
You can request Azure Front Door to return more debugging HTTP response headers. For more information, see [optional response headers](front-door-http-headers-protocol.md#optional-debug-response-headers).
1919

20-
## 503 response from Azure Front Door after a few seconds
20+
## 503 or 504 response from Azure Front Door after a few seconds
2121

2222
### Symptom
2323

24-
* Regular requests sent to your backend without going through Azure Front Door are succeeding. Going via Azure Front Door results in 503 error responses.
24+
* Regular requests sent to your backend without going through Azure Front Door are succeeding. Going via Azure Front Door results in 503 or 504 error responses.
2525
* The failure from Azure Front Door typically appears after about 30 seconds.
2626
* Intermittent 503 errors appear with "ErrorInfo: OriginInvalidResponse."
2727

0 commit comments

Comments
 (0)