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-performance-issues.md
+25-43Lines changed: 25 additions & 43 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,65 +41,47 @@ If one of the origin servers is slow, then the first request for an object via A
41
41
42
42
To check response headers, use the following `curl` examples in Bash. You can also use your browser's developer tools by selecting the F12 key. Select the **Networking** tab, select the relevant file to be investigated, and then select the **Headers** tab. If the file is missing, reload the page with the developer tools open.
43
43
44
-
The initial response should have an `x-cache` header with a `TCP_MISS` value. The Azure Front Door POP forwards requests with this value to the origin. The origin sends the return traffic on that same path to the requesting client.
44
+
The initial response should have an `x-cache` header with a `TCP_MISS`or `CONFIG_NOCACHE`value. The Azure Front Door POP forwards requests with this value to the origin. The origin sends the return traffic on that same path to the requesting client.
1. Continue to request against the endpoint until the `x-cache` header has a `TCP_HIT` value.
82
+
83
+
If you initially saw `CONFIG_NOCACHE`, then caching is not enabled in the route configuration. In this case, you will not see `TCP_HIT`.
84
+
103
85
1. If the performance problem is resolved, the problem was based on the origin's speed and not the performance of Azure Front Door. The owner needs to address the Azure Front Door cache settings or the origin to improve performance.
104
86
105
87
If the problem persists, the source might be the client that's requesting the content or the Azure Front Door service. Move to Scenario 2 to identify the source.
0 commit comments