Bug #31240
closed
compressor and clients without gzip as accepted encoding
0%
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
- 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.
Updated by Alexander Opitz almost 10 years ago
- Status changed from Accepted to Needs Feedback
- Is Regression set to No
Hi,
as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (6.2.7)?
Updated by Alexander Opitz over 9 years ago
- Status changed from Needs Feedback to Closed
No feedback within the last 90 days => closing this issue.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.