CDN
Platform response headers
Platform response headers Easel CDN adds on every deployment.
Easel CDN adds a small set of response headers on every request. Use them for debugging, observability, and correlating edge decisions with your logs.
Response headers
| Header | Description |
|---|---|
X-Easel-Id | Unique id for this request. Include it when you contact support. |
X-Easel-Cache | CDN cache status (HIT, MISS, BYPASS, STALE, or ERROR). See Caching. |
Server | Always Easel on CDN responses. |
Strict-Transport-Security | HTTP Strict Transport Security (HSTS) (max-age=63072000) on HTTPS responses. |
X-Robots-Tag | On preview deployments: noindex, nofollow, noarchive. |
X-Easel-Firewall-Action | Firewall decision when a rule or challenge applies (for example deny, challenge, throttle). |
X-Easel-Firewall-Rule-Id | Identifier of a matching custom Web Application Firewall (WAF) rule when present. |
Challenge flows also use headers such as X-Easel-Challenge-Token and X-Easel-Mitigated. See WAF and attack challenge for those details.
Headers Easel removes
Easel strips internal platform headers before the response reaches the browser. Easel ignores client-injected internal headers on the request; they do not affect routing or which project serves the request.
Do not rely on undocumented x-easel-* headers in application code. Prefer the table above and the security docs for the supported contract.