Skip to content

Commit 18c3097

Browse files
Merge pull request #285722 from RussellR-MSFT/patch-1
ANPTA: Front Door - troubleshooting performance issues (fix PII information)
2 parents 774323d + c14373f commit 18c3097

File tree

1 file changed

+25
-43
lines changed

1 file changed

+25
-43
lines changed

articles/frontdoor/troubleshoot-performance-issues.md

Lines changed: 25 additions & 43 deletions
Original file line numberDiff line numberDiff line change
@@ -41,65 +41,47 @@ If one of the origin servers is slow, then the first request for an object via A
4141

4242
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.
4343

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.
4545

4646
Here's an example that shows `TCP_MISS`:
4747

4848
```bash
49-
$ curl -I "https://S*******.z01.azurefd.net/media/EteSQSGXMAYVUN_?format=jpg&name=large"
49+
$ curl -I https://www.contoso.com/styles.css
5050
HTTP/2 200
51-
cache-control: max-age=604800, must-revalidate
52-
content-length: 248381
53-
content-type: image/jpeg
54-
last-modified: Fri, 05 Feb 2021 15:34:05 GMT
55-
accept-ranges: bytes
56-
age: 0
57-
server: ECS (sjc/4E76)
58-
x-xcachep2c-originurl: https://p****.com:443/media/EteSQSGXMAYVUN_? format=jpg&name=large
59-
x-xcachep2c-originip: 72.21.91.70
60-
access-control-allow-origin: *
61-
access-control-expose-headers: Content-Length
62-
strict-transport-security: max-age=631138519
63-
surrogate-key: media media/bucket/9 media/1357714621109579782
51+
date: Wed, 28 Aug 2024 17:02:09 GMT
52+
content-type: text/css
53+
content-length: 2837
54+
last-modified: Thu, 09 May 2024 20:49:36 GMT
55+
etag: "b15-6180b8e9bd897"
56+
vary: Accept-Encoding
57+
x-azure-ref: 20240828T170209Z-AA11BB22CC33DD44EE55FF66AA77BB88CC99DD00
58+
x-fd-int-roxy-purgeid: 0
6459
x-cache: TCP_MISS
65-
x-connection-hash: 8c9ea346f78166a032b347a42d8cc561
66-
x-content-type-options: nosniff
67-
x-response-time: 26
68-
x-tw-cdn: VZ
69-
x-azure-ref-originshield: 0MlAkYAAAAACtEkUH8vEbTIFoZe4xuRLOU0pDRURHRTA1MDgAZDM0ZjBhNGUtMjc4
70-
x-azure-ref: 0MlAkYAAAAACayEVNiWaKRI61MXUgRe97REFMRURHRTEwMTQAZDM0ZjBhNGUtMjc4
71-
date: Wed, 10 Feb 2021 21:29:22 GMT
60+
accept-ranges: bytes
7261
```
7362

7463
Here's an example that shows `TCP_HIT`:
7564

7665
```bash
77-
$ curl -I "https://S*******.z01.azurefd.net/media/EteSQSGXMAYVUN_?format=jpg&name=large"
66+
curl -I https://www.contoso.com/styles.css
7867
HTTP/2 200
79-
cache-control: max-age=604800, must-revalidate
80-
content-length: 248381
81-
content-type: image/jpeg
82-
last-modified: Fri, 05 Feb 2021 15:34:05 GMT
83-
accept-ranges: bytes
84-
age: 0
85-
server: ECS (sjc/4E76)
86-
x-xcachep2c-originurl: https://p****.com:443/media/EteSQSGXMAYVUN_?format=jpg&name=large
87-
x-xcachep2c-originip: 72.21.91.70
88-
access-control-allow-origin: *
89-
access-control-expose-headers: Content-Length
90-
strict-transport-security: max-age=631138519
91-
surrogate-key: media media/bucket/9 media/1357714621109579782
68+
date: Wed, 28 Aug 2024 17:04:38 GMT
69+
content-type: text/css
70+
content-length: 2837
71+
last-modified: Thu, 09 May 2024 20:49:36 GMT
72+
etag: "b15-6180b8e9bd897"
73+
vary: Accept-Encoding
74+
x-azure-ref: 20240828T170438Z-BB22CC33DD44EE55FF66AA77BB88CC99DD00EE11
75+
x-fd-int-roxy-purgeid: 0
9276
x-cache: TCP_HIT
93-
x-connection-hash: 8c9ea346f78166a032b347a42d8cc561
94-
x-content-type-options: nosniff
95-
x-response-time: 26
96-
x-tw-cdn: VZ
97-
x-azure-ref-originshield: 0MlAkYAAAAACtEkUH8vEbTIFoZe4xuRLOU0pDRURHRTA1MDgAZDM0ZjBhNGUtMjc4Mi00OWVhLWIzNTYtN2MzYj
98-
x-azure-ref: 0NVAkYAAAAABHk4Fx0cOtQrp6cHFRf0ocREFMRURHRTEwMDUAZDM0ZjBhNGUtMjc4Mi00OWVhLWIzNTYtN2MzYj
99-
date: Wed, 10 Feb 2021 21:29:25 GMT
77+
x-cache-info: L1_T2
78+
accept-ranges: bytes
10079
```
10180

10281
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+
10385
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.
10486

10587
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

Comments
 (0)