[Tickets #1626] NEW: Using ZPS file compression incompatible with compress_pages option

[bugs at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=1626
-----------------------------------------------------------------------
 Ticket             | 1626
 Created By         | kevin_myer at iu13.org
 Summary            | Using ZPS file compression incompatible with compress_pages option
 Queue              | Horde Base
 Version            | 3.0.3
 State              | Unconfirmed
 Priority           | 1. Low
 Type               | Bug
 Owners             | 
-----------------------------------------------------------------------


kevin_myer at iu13.org (2005-03-25 17:45) wrote:

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.