For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
HUMAN DashboardHUMAN WebsiteRequest a Demo
Product GuidesEnforcer GuidesMobile SDKAPI ReferenceCustomer support
Product GuidesEnforcer GuidesMobile SDKAPI ReferenceCustomer support
  • General
    • About Enforcers
    • Support first-party HUMAN calls
    • Troubleshoot Enforcer configurations
  • Enforcer frameworks
    • Akamai ESI
      • Akamai ESI changelog
      • Installation
      • Configuration
      • First Party Configuration
    • Apache - C Module
    • ASP.NET
    • Callout Enforcer
    • Envoy Proxy
    • F5 BIGIP
    • Fastly JavaScript Compute@Edge
    • Google Cloud Platform (GCP) Callout Enforcer
    • Kong Plugin
    • NGINX - C Module
    • NGINX - LUA Module
    • PHP
    • Python
    • Ruby
    • Salesforce Commerce Cloud Cartridge
LogoLogo
Login
Login
HUMAN DashboardHUMAN WebsiteRequest a Demo
On this page
  • Overview
Enforcer frameworks

Akamai ESI

Overview

This guide describes how to install and configure HUMAN Akamai ESI (Edge Side Includes) Enforcer.

Akamai ESI Enforcer is based on the following Akamai CDN features:

  • Akamai Property Manager - Akamai’s configuration application. Using the Property Manager, customers can set the way Akamai’s edge servers behave for the end user’s request.
  • Akamai NetStorage - Akamai’s cloud storage.

The HUMAN Akamai ESI Enforcer is made up of configuration settings set on the Akamai Property Manager and ESI (Edge Side Includes) files stored on the customer’s NetStorage.

Was this page helpful?
Previous

Akamai ESI changelog

Next
Built with