| Summary | Using ZPS file compression incompatible with compress_pages option |
| Queue | Horde Base |
| Queue Version | 3.0.3 |
| Type | Bug |
| State | Resolved |
| Priority | 1. Low |
| Owners | chuck (at) horde (dot) org |
| Requester | kevin_myer (at) iu13 (dot) org |
| Created | 03/26/2005 (7417 days ago) |
| Due | |
| Updated | 04/22/2005 (7390 days ago) |
| Assigned | 03/26/2005 (7417 days ago) |
| Resolved | 04/22/2005 (7390 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
resolved the problem.
State ⇒ Resolved
was on. Let me know if what I committed fixes this for you.
The suggestion was made to test for the existence of ZPS file
compression by checking the values of:
zend_accelerator.compress_all
or
zend_accelerator.compression
So I'd think that just adding a check to see if
zend_accelerator.compress_all !=1 or
ini_get('zend_accelerator.compress_all) == '' (I'm not sure which is
the proper way to do it, my guess would be the latter) in
Horde::compressOutput should do the trick.
I have all my sites accelerated currently and don't want to monkey
with configs in the middle of the day. But I'll add a php_admin_value
to disable ZPS compression for my test site and will either generate a
patch or test one if you beat me to it.
Assigned to Chuck Hagenbuch
State ⇒ Feedback
ini_get('output_handler')? Or is there another ini option fo the zps
compression? Look in Horde::compressOutput() to see what I'm getting
at - we need to modify the check there.
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Using ZPS file compression incompatible with compress_pages option
Queue ⇒ Horde Base
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.