Tickets :: Comment on [#1626] Using ZPS file compression incompatible with compress

* Your Email Address
* Spam protection	Enter the letters below: __.. ..___..__ . . (__ \|\ \| \| [ __\|__\| .__)\| \\| \| [_./\| \|
Comment	> ZPS contains a file compression option. If Horde is configured to > use zps4, and if file compression is turned on in ZPS, and if Horde > is configured with compress_pages=true, Horde is unuseable. All > pages come up with: > > > > Notice ob_end_clear(): failed to delete buffer Zend Cache Compressor. > followed by random garbage (which I'm assuming is maybe multiply > compressed output) > > > > I believe the ob* functions are being called multiple times and the > two attempts at compression are conflicting. It would be nice if > conf.xml warned the user of the potential conflict, or automatically > disabled compress_pages if using ZPS (although perhaps not everyone > would have file compression turned on in ZPS). > > > > My testing showed a remarkable improvement in page response time when > using ZPS file compression, versus using Horde's compress_file option.
Attachment
Watch this ticket