zlib.output_compression

[trogladyte]

I always turn on Gzip in the CMS, plus I have deflate in .htaccess. I recently noticed zlib.output_compression in my PHP settings and it was off. Should I turn it on? Would it do anything?

This is my deflate lines in .htaccess:

SetOutputFilter DEFLATE
Header set Expires "max-age=29030400, public"
Header unset ETag
FileETag None

[davidnguyen]

Hi,

Not sure but Gzip is more relevant to webserver configuration

[GerogescuM]

Gzip compresion is more server related. You should not worry to do this in the cms.
Another server related optimization you should check, is if you have the lastest PHP version.

[trogladyte]

OK, but should I use that instead of Joomla's GZip compression (in the admin Config)? Neither reply really addresses that. And, yes, right now I have the latest (bar one if you include 8.0) PHP version.

[GerogescuM]

OK, but should I use that instead of Joomla's GZip compression (in the admin Config)? Neither reply really addresses that. And, yes, right now I have the latest (bar one if you include 8.0) PHP version.

Use server compression. It's much faster and safe (no other conflicts).
Plus you won't have to enable it on every singe site from your server.

[shoulders]

for the end user gzip and deflate are the same. mod_deflate is gzips replacement.

enabling gzip in joomla compresses the HTML content and makes sure the correct headers are sent.

the zlib.output_compression is a php option that will enforce all text content to be compressed and the appropriate headers to be sent.

if joomla detects his php option is enabled it behaves appropriately and let's php add the headers and do the compression.

I doubt there is much speed difference between the 2.