@jaswsinc
Thanks for the note, >0 actually makes sense. Probably during my tests there were always at least 2 output filters active. I will have a look at this again.
Thanks for the fast reply Arnee; and also for taking a look at this.
OK, so I will just tell anyone who asks us about this that you’re working on a fix for a future release then. Great! Updating this GH issue: https://github.com/websharks/quick-cache/issues/105#issuecomment-46363603
Hi,
after further testing, I think i will keep it at 0. The recommended value for “output_buffering” in the php.ini is 4096, which means that there will be always one output buffer (“default output handler” in ob_list_handlers) and the level will be always at least 1.
http://de.php.net/manual/en/outcontrol.configuration.php#ini.output-buffering
php.ini (default for production)
; Output buffering is a mechanism for controlling how much output data
; (excluding headers and cookies) PHP should keep internally before pushing that
; data to the client. If your application's output exceeds this setting, PHP
; will send that data in chunks of roughly the size you specify.
; Turning on this setting and managing its maximum buffer size can yield some
; interesting side-effects depending on your application and web server.
; You may be able to send headers and cookies after you've already sent output
; through print or echo. You also may see performance benefits if your server is
; emitting less packets due to buffered output versus PHP streaming the output
; as it gets it. On production servers, 4096 bytes is a good setting for performance
; reasons.
; Note: Output buffering can also be controlled via Output Buffering Control
; functions.
; Possible Values:
; On = Enabled and buffer is unlimited. (Use with caution)
; Off = Disabled
; Integer = Enables the buffer and sets its maximum size in bytes.
; Note: This directive is hardcoded to Off for the CLI SAPI
; Default Value: Off
; Development Value: 4096
; Production Value: 4096
; http://php.net/output-buffering
output_buffering = 4096
Ok, one more option: I will check if the output_buffering of PHP is active and compare the level to > 1 if true. That should catch the PHP settings as well as additional output buffers.
Ah, right. That sounds great.
Changes are committed to trunk, let me know if you still have problems!
Great, thank you. I will test shortly and report back.
Yes, that did the trick. Thanks so much!
Great, thanks for the feedback.