Response Headers

Edgemesh Client and Server add headers to each response to help shed light on how a request was routed.
Client Headers
X-Edgemesh-Client
The X-Edgemesh-Client header is added when the Edgemesh Client was able to service a Request.
Value
Description
origin
The request was routed to the origin server over the internet.
cached
The request was served from the Edgemesh Browser Cache and the Response was cached by this browsers previous requests to the resource.
precached
The request was served from the Edgemesh Browser Cache and the Response was cached by the Edgemesh prefetching algorithm.  The asset was cached before the browser requested it.
Server Headers
X-Edgemesh-Server
The X-Edgemesh-Server header is added when a Request is routed through Edgemesh Server.  The format for the header is Cache Status,Request Routing Strategy,Edgemesh Server Plugin.
Cache Status
Value
Description
miss
The Request was not cached at the edge and was served from the origin backend. 
hit
The Request was served entirely from the edge cache.
hybrid
The Request was partially served from the edge cache and partially served from the origin backend.
Request Routing Strategy
Value
Description
bypass
The Request has bypassed Edgemesh Server Optimizations.  This is the value when ?em-bypass=server is set.
forward
The Request did not meet the criteria to be serviced by Edgemesh Server and was forwarded to the backend server.
direct
The Request was responded to directly by Edgemesh Server.  This value is set when a Request did not require a backend Fetch.
proxy
The Request was served with Edgemesh Server Optimizations.
prerendered
The Request was prerendered by Edgemesh Server.  These responses are served to known bots and search engines. 
Edgemesh Server Plugin
Value
Description
shopify
The Edgemesh Server Shopify Plugin served this Request.
Server-Timing
Edgemesh Server adds Server-Timing metrics that breaks down performance metrics for each individual function during a Request's path to being served a Response.  This is used for internal debugging and performance monitoring, but is also visible in the Network Panel on each Response. All of the duration values are in milliseconds.
Value
Description
Cache Hit
The Edgemesh edge cache was hit.
Cache Miss
The Edgemesh edge cache was missed.
Cookies Appended
Cookies were appended to the cached response.
Get Config
The time it takes to get the configuration for the request.
Parse URL
The time it takes to parse the Request URL.
Parse Body
The time it takes to parse the Response body.
Rewrite URL
The time it takes to rewrite the URL.
Rewrite Response
The time it takes to rewrite (optimize) the response body.
Should Forward
The time it takes to determine if a Request should be forwarded.
Sitemap Validate
The time it takes to determine if a request is a sitemap.
Cache Lookup
The time it takes to lookup an object in cache.
Cache Set
The time it takes to set an object in cache.
Create Request
The time it takes to create the backend Request.
Create Response
The time it takes to create the Response.
Create Cookie Request
The time it takes to create a HEAD request to fetch cookies.
Backend Fetch
The time it takes to fetch a request from the backend server.
Cookies Fetch
The time it takes to fetch and append cookies to a cached Response.
​

Reference - Previous

API

Next - Deprecations

OnLoad

Last modified 11mo ago

Copy link

On this page

Client Headers

X-Edgemesh-Client

Server Headers

X-Edgemesh-Server

Server-Timing