Question about x-litespeed-cache name

#1
Hello,

I have a client that need to hide all header information about the webservers in use, so we recompiled nginx (reverse proxy) to hide the server signature, and then we disabled the response "x-turbo-charged-by: litespeed" using proxy_hide_header in the proxy.

However we still get a "x-litespeed-cache: hit" from the LiteSpeed Cache.

My question is: Can we rename this header to something like "x-cache-status" using the proxy? Or does the plugin/lscache mechanism use this specific header value to do something internal, much like ngx_pagespeed uses the x-page-speed header to avoid loops?

Thanks
 
Last edited:
Top