Alokai Classic vs Alokai@Edge

Alokai offers two deployment options: Alokai Classic and Alokai@Edge.

X-Origin-Host and Multistore

Alokai@Edge automatically adds the X-Origin-Host header to preserve the original customer-facing domain. This is important for multistore setups using domain-based routing, as the Host header gets rewritten to the internal Alokai infrastructure domain.

For multistore configurations using the Config Switcher's domain strategy, X-Origin-Host ensures reliable domain detection when routing requests to the correct store configuration.

Migration

If you're migrating from Alokai Classic to Alokai@Edge:

• Update code: If your code reads x-forwarded-host directly, update it to use x-origin-host instead
• Test your multistore routing with all store domains
• Review any custom header handling in your code
• Plan DNS cutover to the edge network

Contact Alokai support for migration assistance.