Distil adds custom HTTP headers to provide additional meta information on HTTP requests and responses. These headers are useful for verifying connectivity with the Distil network, troubleshooting, and log integration.
Request headers are not visible in a web browser. They exist only between a Distil edge node and your origin server.
X-Distil-Bot – Shows the threat value of the request. The X-Distil-Bot header carries the threat value from the Distil edge node to the origin server. Distil assigns threat values to requests to determine how to handle each request.
For more information on threat values, please see Web X-Distil-Bot Values.
X-Forwarded-For (Distil usage) – Contains the original client's IP address. The Distil server changes the value of the remote_addr header to one of Distil’s edge node IP addresses. The Distil server creates the X-Forwarded-For header and places the true client's IP address in the header.
For more information on the X-Forwarded-For header, please see Logging Integration.
X-Forwarded-For-Old – Distil adds this header when a request comes to Distil with an X-Forwarded-For header already in place. Distil moves the value in the X-Forwarded-For field into the X-Forwarded-For-Old field. Often, this happens when a request comes to Distil after traveling through a previous proxy service.
X-Distil-BrowserType – Distil adds this header to a request when the customer enables mobile caching. This header will contain either the value Standard if the request comes from a traditional web browser or Mobile if the request comes from a mobile user agent. Customers can use this header to let Distil handle mobile browser detection, rather than relying on the origin server to detect mobile browsers.
X-Distil – Distil adds this header to every request. Distil attaches a randomized token to the header that's unique for every domain. X-Distil allows the customer to verify from the randomized token that the request came from Distil.
X-Distil-CS – Shows the cache status of the response. Common cache status values are:
- HIT – An object served from cache.
- MISS – An object configured to cache but did not cache at the time of the request.
- BYPASS – An object configured not to use cache.