The diagnostic-tools Developer Hub

Welcome to the diagnostic-tools developer hub. You'll find comprehensive guides and documentation to help you start working with diagnostic-tools as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started    

ESI debugger tool

With ESI Debugger Tool, you can test and debug your web page, just by providing its URL. Additional options will allow you to emulate specific client-browser and geographical conditions.

Before you begin

Your web page must be deployed to either production or test environment.


Your edge server configuration must be set up to allow the edge server to access the domain.

How to

  1. Go to > SUPPORT > Diagnostic Tools .
  2. Go to ESI Debugger.
  3. Type in URL for your web page. You must provide full URL with a protocol, for example:
  4. Optional: To adjust test conditions, change these settings:
    • Client request headers. This field comes with default values. You can change them to simulate any client-browser conditions.
    • Client IP. Use this field to emulate EdgeScape geographic data. To learn more about EdgeScape, visit EdgeScape Users Guide.
    • Test server URL. Use this field if your website is deployed to your test environment.
  5. Click Submit.
    The debugging report is generated.

How to read the results

The ESI Debugger Tool report is split into three sections: environment variables, ESI syntax errors, and evaluation messages.

Environment variablesLists all environment variables used for the test. To change these values before the test, use the Client Request Headers field.
ESI syntax errorsLists all errors found in the ESI code. Each error has a reference code and a brief message. Check ESI syntax messages for a more detailed description of each error code.
Evaluation messagesLists all evaluation messages triggered during the test. Each line has a reference code and a brief message. Check Evaluation messages for more details.

Updated about a month ago

ESI debugger tool

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.