On a new install where wp-super-cache is trying to serve it's own pre-compressed files, litespeed seems to be sending them as binary when apache gets it right. Perhaps I need to exclude recompressing them somehow? Works fine in apache, litepspeed serves garbled (looks like native gzip) Headers are almost indentical. litespeed apache So the content type is the same and the critical content-encoding is there. But my guess is that litespeed sees text/html content-type and tries to re-encode it with gzip because the filetype (html.gz) is not excluded. Length is slightly longer which also hints at re-compression with just a repeated compression header. But I do not know how to exclude by extension, litespeed only supports mime-type? Is there any possible easy workaround? I know one solution is just to let litespeed make the gzip in it's own area but client wants apache backwards compatibility.