Issue Bug Closed

#31240compressor and clients without gzip as accepted encoding

Stefan Galinski 10/24/11, 21:11 updated 06/15/15, 10:14

Description

Currently the compressor adds the gzip file encoding depending on the gzip accept-encoding setting of the first client who triggers the page generation. If the second request is triggered by a client who doesn’t supports gzip, he will just get garbage.

Possible Solution:
- Always add .gzip as file extension if the compressionLevel is set
- Provide something like the following inside the example .htaccess file

  1. deliver the uncompressed file if gzip encoding isn’t accepted
    RewriteCond %{HTTP:accept-encoding} !gzip [NC]
    RewriteRule ^typo3temp/scriptmerger/compressed/(.+)\.gz\.(js|css) typo3temp/scriptmerger/uncompressed/$1.$2 [L,NC]

This code was borrowed form the scriptmerger extension and decides the delivered content on a per-client base.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.