Skip to content

Commit e6c2877

Browse files
author
Pablo Gonzalez
committed
fix alt text
1 parent ca22579 commit e6c2877

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

articles/frontdoor/refstring.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Troubleshoot Azure Front Door with RefString
3-
description: This article provides information about what a RefString is and how to gather them
3+
description: This article provides information about what a RefString is and how to gather them.
44
author: Alej-b23
55
ms.author: pagonzalez
66
ms.service: azure-frontdoor
@@ -27,7 +27,7 @@ RefStrings can help you troubleshoot and resolve issues with Azure Front Door, s
2727
> [!NOTE]
2828
> If you encounter an error page from Microsoft services, it will already include a RefString for the request that generated the error page. In such cases, you can skip directly to the diagnostic step.
2929
30-
## How to gather a RefString?
30+
## How to gather a RefString
3131

3232
To gather a RefString, you need to capture the HTTP response headers of the requests and look for the header named **X-Azure-Ref**. This header contains the RefString, encoded in Base64. You can use different methods to capture the HTTP response headers, depending on your preference and situation. Here are a few examples of how to obtain a RefString from various browsers and applications:
3333

@@ -69,32 +69,32 @@ To learn more about viewing and capturing network traffic with Fiddler, see [Web
6969

7070
---
7171

72-
## How to use a RefString with some of our troubleshooting tools?
72+
## How to use a RefString with some of our troubleshooting tools
7373
Azure Front Door uses a RefString to manage 4xx and 5xx errors. The following are the steps to use the diagnostic tool with a RefString for tracking and diagnosing connectivity issues:
7474

7575
1. Navigate to your Azure Front Door Profile.
7676

7777
1. Select the **Diagnose and solve problems** menu.
7878

79-
:::image type="content" source="media/refstring/refstring-step-one-portal.png" alt-text="Diagnosing using RefString step one" lightbox="media/refstring/refstring-step-one-portal.png":::
79+
:::image type="content" source="media/refstring/refstring-step-one-portal.png" alt-text="Screenshot showing the first step in diagnosing problems using a RefString." lightbox="media/refstring/refstring-step-one-portal.png":::
8080

8181
1. Scroll down and select **Connectivity** under the **Common problems** section.
8282

83-
:::image type="content" source="media/refstring/refstring-step-two-portal.png" alt-text="Diagnosing using RefString step two" lightbox="media/refstring/refstring-step-two-portal.png":::
83+
:::image type="content" source="media/refstring/refstring-step-two-portal.png" alt-text="Screenshot showing the second step in diagnosing problems using a RefString." lightbox="media/refstring/refstring-step-two-portal.png":::
8484

8585
1. In the box **What issue are you having?** select **Select a problem subtype** and choose **4xx and 5xx errors** on the drop down-menu, then select the **Next**.
8686

87-
:::image type="content" source="./media/refstring/refstring-step-three-portal.png" alt-text="Diagnosing using RefString step three" lightbox="media/refstring/refstring-step-three-portal.png":::
87+
:::image type="content" source="./media/refstring/refstring-step-three-portal.png" alt-text="Screenshot showing the third step in diagnosing problems using a RefString." lightbox="media/refstring/refstring-step-three-portal.png":::
8888

8989
1. Enter your RefString in the box within the **4xx and 5xx errors** section. You input the Restring given to you from your request under the **Tracking Reference – RefString** field.
9090

91-
:::image type="content" source="media/refstring/refstring-step-four-portal.png" alt-text="Diagnosing using RefString step four" lightbox="media/refstring/refstring-step-four-portal.png":::
91+
:::image type="content" source="media/refstring/refstring-step-four-portal.png" alt-text="Screenshot showing the fourth step in diagnosing problems using a RefString." lightbox="media/refstring/refstring-step-four-portal.png":::
9292

9393
1. Finally, select **Run Diagnostics** to identify the cause of the issue, which explains the failure if it's a known problem.
9494

9595
An example of a result displaying an issue:
9696

97-
:::image type="content" source="media/refstring/refstring-example.png" alt-text="Diagnosis example using RefString" lightbox="media/refstring/refstring-example.png":::
97+
:::image type="content" source="media/refstring/refstring-example.png" alt-text="Screenshot showing an example of the diagnosis at work using a RefString." lightbox="media/refstring/refstring-example.png":::
9898

9999
> [!NOTE]
100100
> The diagnostic capabilities may require up to 15 minutes to deliver results. We ask for your patience that you allow the process to finish before taking further action.

0 commit comments

Comments
 (0)