Queue-it Connector for Akamai

The package enables you to add traffic management support to your website. The Connector Implementation Guide can be found via the Queue-it GO Platform | Help | Connector Integration Documentation. In order to get access please reach out to your Queue-it representative.

Entry points

The package mirrors the two released EdgeWorker bundles as subpath entry points. Your EdgeWorker main.js should re-export the handlers of exactly one execution flow — Akamai invokes every handler your bundle exports, so mixing flows causes double executions.

Client-request flow (default — validates queue status on every request, same as kuedge.customerhosted.tar.gz):

export { onClientRequest, onClientResponse } from "@queue-it/akamai-connector/onclient";

Origin-request flow (validates on cache misses only, same as kuedge.customerhosted.onorigin.tar.gz — no PMUSER_BYPASS_EW_CLTREQ_EVENT variable needed; see the "Using the onOrigin Bundle" section of the integration guide for the property requirements):

export { onOriginRequest, onOriginResponse, onClientResponse } from "@queue-it/akamai-connector/onorigin";

Never import from both subpaths in the same bundle — the entry points configure the connector's execution mode at import time, and the second import would reconfigure the whole module graph.

The root entry (@queue-it/akamai-connector) remains for backwards compatibility: it exports all four handlers with the execution mode controlled at runtime by the PMUSER_BYPASS_EW_CLTREQ_EVENT property variable. New integrations should prefer the subpath entry points, which need no property variable.