Edgemesh® Client Custom Headers

When Edgemesh® Client serves a request, it adds useful response headers to provide insights into the caching and acceleration process. These headers can be utilized to understand how Edgemesh® Client handles the request and whether the response is served from the origin or from the cache. Here are some examples of the response headers:

• X-Edgemesh-Client: origin: This header indicates that the response is served directly from the origin server without any Edgemesh® Client caching or acceleration.

• X-Edgemesh-Client: cached: This header signifies that the response is served from the Edgemesh® Client cache. It indicates that the requested resource has been previously cached by Edgemesh® Client and can be delivered directly from the cache without making a request to the origin server.

• X-Edgemesh-Client: precached: This header indicates that the requested resource has been preloaded or prefetched in advance by Edgemesh® Client. It implies that the resource is available in the cache even before it is explicitly requested, resulting in faster subsequent requests.

These response headers provide valuable information about how Edgemesh® Client handles the request and whether caching or acceleration is involved. You can inspect these headers in the network tab of your browser's developer tools or programmatically access them in your application.