Request Content (CURL)

The Request Content (CURL) tool provides the raw HTML for a URL, including request headers. You can run this operation for a specific location, an edge IP, or Site Shield map.

You can use this tool to:

  • Verify if a user of the IP address can connect to a URL.
  • Check request and response headers.
  • Test the URL with interjected headers.

You can also use the compare results feature. It may help you identify the difference causing issues.

Submit a request

Learn how to submit a request for the Request Content (CURL) tool.

There are four possible combinations for submitting the request:

1 URL and multiple edge server IP addresses.
This verifies if a URL looks the same on different edge servers.
1 URL for IPs
1 URL and multiple locations.
This verifies if a URL is displayed to users in different locations in the same way.
1 URL for Locations
Multiple URLs and a single edge server IP address.
This verifies how multiple URLs look on the particular edge server.
URLs for IP
Multiple URLs and a single location.
This verifies how multiple URLs are displayed to users from a particular location.
URLs for Locations


  • The URL is the website you want to get the data for.
  • Locations are cities closest to your users.
  • Edge server IPs are IPs you want to get the URL's raw HTML from.

To submit a request:

  1. Go to > SUPPORT > Edge Diagnostics.

  2. In the side menu, select > Request Content (CURL).

  3. Follow the steps for the preferred option:

    1 URL optionMultiple URLs option
    a) In the URLs field, enter one fully qualified URL you want to get a cURL response for.
    b) Select whether you want to get data for multiple Locations or Edge server IPs. Enter up to 10 values.
    a) Enter up to 10 fully qualified URLs you want to get a cURL response for.
    b) Select whether you want to get data for Locations or Edge server IPs. Enter one value.
  4. If you want to run cURL using the Site Shield map, select the Run from site shield map checkbox. When selected, Edge Diagnostics uses the entered location or edge server IP to find the Site Shield map for the URL's hostname and runs the tool using the map. Currently, ZAM hostnames are not supported.

  5. Optional: Into the Spoof to edge server IP field, enter the edge server IP you want to serve traffic from. To get this data, you can use User Diagnostic Data or Get Domain Details (DIG) tools' results.

  6. Select the IP version for which you want to get the data.

  7. Optional: Add a Request header to simulate user traffic and for debugging purpose. It needs to follow the format: Header: value. For example, 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 this list of user agents for possible values.

    1. Click Add another header to add more request headers.
    2. To add ​Akamai​ Pragma headers, click Add Pragma headers. To learn more about ​Akamai​ Pragma headers, check Pragma headers.
  8. Click Submit.

What you should see
If you entered more than one URL and location or edge server IP, Edge Diagnostics divides your input; one request per URL/location or URL/edge server IP pair. All requests appear in the Recent requests table. Click Username icon in the table's corner to see only your requests.

Next steps
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.


In the Response section, you can see the returned HTTP status code and returned Headers.

Headers contain the URL’s response headers. The most common response headers are:

  • Server. The name for the response’s web server.
  • Connection. Options for the current connection.
  • Date. The RFC 2616 formatted date of this response.
  • Expires. The RFC 2616 formatted date for when the request becomes stale.
  • Content-Length. The number of bytes served.
  • Content-Type. The content’s MIME type.
  • Mime-Version. The MIME version.

For the full list of possible response headers, check HTTP headers.


The URL may also have additional Akamai response headers. It’s names and values depend on your products.

You can download the response body by clicking Download in the response Body section.


Response body limitations

  1. For URLs with potentially malicious .exe, .scr, .pdf, .vbs, .rtf, .doc, .xls, .com, .bat, .cmd, .msi, .bin, .sh, .deb, .sh, .deb, .rpm, .tar, .sys, .dll extensions in a path or query parameter the response body has 0 bytes.
  2. The non-0 bytes response body is returned only for text/html, text/plain, text/xml, application/json, and application/xml content type.

Compare results

With the Compare results feature, you can compare the status and response headers for two requests. It may help you identify the difference in URL’s settings causing issues.

  1. Open the Request Content (CURL) tool.
  2. In the Recent requests table, select two requests and in the table's top corner, click Compare results.

What you should see
Edge Diagnostics compares the results for selected URLs. The differences in Status and Response headers are highlighted.