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/frontdoor/troubleshoot-issues.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,11 +17,11 @@ This article describes how to troubleshoot common routing problems that you migh
17
17
18
18
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).
19
19
20
-
## 503 response from Azure Front Door after a few seconds
20
+
## 503 or 504 response from Azure Front Door after a few seconds
21
21
22
22
### Symptom
23
23
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.
25
25
* The failure from Azure Front Door typically appears after about 30 seconds.
26
26
* Intermittent 503 errors appear with "ErrorInfo: OriginInvalidResponse."
0 commit comments