Guide
TrainingSupportCommunity

Content Problems

Suggest Edits

The Content Problems is one of the available Problem scenarios.

Content Problems lets you quickly gather all diagnostic data for a URL required to identify an issue. It combines Request Content (CURL), and View Logs (GREP) tools.

Submit a request

Learn how to submit a request in the Content Problems scenario.

There are two ways in which you can submit a Content Problems request, Basic and Advanced.
Use the Basic mode, if you don't know exact data necessary to get cURL and GREP data. The Advanced mode lets you select all request's details.

Basic request

To submit a basic request:

  1. Go to ☰ > SUPPORT > Edge Diagnostics.

  2. In the side menu, select > Content Problems.

  3. Enter a URL experiencing issues.

  4. Select the location closest to your user.

  5. If you want to run the scenario using the Site Shield map, select the Run from site shield map checkbox. When selected, Edge Diagnostics uses the entered location to find the Site Shield map for the URL's hostname and runs the scenario using the map.

    📘

    ZAM hostnames

    With the Run from site shield map checkbox selected, the tool doesn't support zone apex mapped (ZAM) URLs.

  6. Select an edge server IP you want to serve traffic from.

  7. Click Submit.

Advanced request

To submit an advanced request:

  1. Go to ☰ > SUPPORT > Edge Diagnostics.

  2. In the side menu, select > Content Problems.

  3. Click Advanced next to the Submit a new request label.

  4. Enter a URL experiencing issues.

  5. Select the location closest to your user.

  6. If you want to run the scenario using the Site Shield map, select the Run from site shield map checkbox. When selected, Edge Diagnostics uses the entered location to find the Site Shield map for the URL's hostname and runs the scenario using the map.

    📘

    ZAM hostnames

    With the Run from site shield map checkbox selected, the tool doesn't support zone apex mapped (ZAM) URLs.

  7. Select an edge server IP you want to serve traffic from.

  8. Add data to use in the cURL request:

    1. Select the IP version to use, either IPv4 or IPv6.
    2. Add a request header to simulate user traffic and for debugging purpose. Each field accepts ony one value and it needs to follow the format: Header: value. For example, Pragma: no-cache or User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.169 Safari/537.36.
      Check Pragma headers and this list of user agents for possible values.
    3. Optional: Click Add another header to add more headers. You can add up to 10 headers.

  9. Click Submit.

Results

Edge Diagnostics adds your request to the Recent requests table. Click Username icon in the table's corner to see only your requests.

Click your request’s row to check the results. If you see Wrong icon in the Actions column, it means, that your request could not be processed and you need to retry.

The Results page is divided into two sections. At the top of the page, you see your request data. Below, you have all the collected data.

  • Summary. The Summary tab results start with the basic data about the URL. This data is followed by unexpected results coming from other tabs, which require your analysis.
  • Content (CURL) tab. To learn more about results in this tab, check Request Content (CURL) results.
  • Logs (GREP) tab. To learn more about results in this tab, check Logs preview.

Updated 3 months ago