Top navigation panel does not load on storefront

This article provides configuration solutions to the Varnish Edge Side Includes (ESI) issues, where certain pages’ content, usually the top navigation panel, is not displayed on the storefront if Varnish is used for caching.

Affected products and versions

  • Adobe Commerce 2.X.X
  • All Varnish versions



Install and configure Varnish for your Adobe Commerce store.

Steps to reproduce:

  1. Go to the storefront.
  2. Browse through the store pages.

Expected results:

All content and all page blocks load successfully.

Actual results:

Observe that some content blocks, like the top navigation panel with categories, are not loading. Blank space is displayed instead.


The possible reasons for the issue are the following:

  • ESI include tags are generated with HTTPS access protocol, while Varnish only works with HTTP.
  • Varnish does not process ESI inside JSON.
  • Response headers are too big for Varnish; it cannot process them.


To resolve the issues, you need to perform an additional Varnish configuration and restart Varnish.

  1. As a user with root privileges, open your Vanish configuration file in a text editor. See the Modify the Varnish system configuration in our developer documentation for info on where this file might be located for different operating systems.

  2. In the DAEMON_OPTS variable, add -p feature=+esi_ignore_https, -p feature=+esi_ignore_other_elements, -p feature=+esi_disable_xml_check. This would look like:

    code language-bash
    DAEMON_OPTS="-a :6081 \    -p feature=+esi_ignore_other_elements \    -p feature=+esi_disable_xml_check \    -p feature=+esi_ignore_https \    -T localhost:6082 \    -f /etc/varnish/default.vcl \    -S /etc/varnish/secret \    -s malloc,256m"
  3. Save your changes and exit the text editor.

  4. In the VCL configuration file, increase the response headers by increasing the values of these parameters: http_resp_hdr_len, http_resp_size, workspace_backend. Make sure that the last two of them have similar values.

  5. When you change this, you need to run service varnish restart for the changes to take effect.