X-Turbo-Charged-By
When an OpenLiteSpeed server answers a request that arrived through a trusted proxy such as Cloudflare, the X-Turbo-Charged-By unofficial response header appears as a branding indicator naming the server software.
Usage
OpenLiteSpeed adds the X-Turbo-Charged-By header to responses when the request reaches the server from behind a trusted proxy, a common setup with Cloudflare in front of the origin. LiteSpeed publishes no documentation for the header. Community reports tie the header to OpenLiteSpeed deployments behind a proxy, with the value naming the LiteSpeed engine rather than reflecting caching activity.
The header acts as a server branding indicator, similar
to the Server header but specific to
LiteSpeed-powered hosting stacks. Administrators
concerned about exposing server details remove the
header through the server's Server Signature setting or
a reverse proxy using proxy_hide_header.
Values
LiteSpeed
The only known value is LiteSpeed, naming the server
software family that generated the response.
Example
A response from an OpenLiteSpeed server running behind a
proxy includes this header. The value LiteSpeed names
the server software.
X-Turbo-Charged-By: LiteSpeed
A typical response from a LiteSpeed-powered hosting stack includes several related headers. The Server header names the server software, X-LiteSpeed-Cache reports the caching layer's outcome, and X-Turbo-Charged-By adds the branding signature.
Server: LiteSpeed
X-Turbo-Charged-By: LiteSpeed
X-LiteSpeed-Cache: hit