Generated .gz files in uploads getting 404

I have WP Super Cache (1.5.9) enabled in Simple mode with compression also enabled (as recommended). Files comprised within wp-content/uploads are being converted automatically to corresponding .gz files. That is, “foo.pdf” is replaced by “foo.pdf.gz”. But http requests for the orginal “foo.pdf” file are now getting 404-not-found responses.

Is it WP Super Cache that is converting files to .gz equivalents? If so, why is it not then responding with the gzipped file version when the file is requested?

We do not use .htaccess for our apache config. Instead we use server level rules. Is this the problem? Does WP Super Cache need special config or rewrite rules to handle this case? If so, how can I determine what those rules should be?

I am experimenting with ad-hoc rewrite rules to deliver (for example) foo.pdf.gz with gzip encoding when foo.pdf is requested. Seems to work but also feels like a big kluge with issues in the returned content-type. And what clients that can’t accept gzip encoding?

• This topic was modified 6 years, 7 months ago by fredcy.