#19436 [Opn->Fbk]: zlib.output_compression causing corruption

From: Date: Thu, 13 Feb 2003 05:56:41 +0000
Subject: #19436 [Opn->Fbk]: zlib.output_compression causing corruption
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-32977@lists.php.net to get a copy of this message
ID: 19436 Updated by: sniper@php.net Reported By: steveh@brendata.co.uk -Status: Open +Status: Feedback Bug Type: Zlib Related Operating System: redhat linux 7.3 PHP Version: 4CVS-2002-09-16 New Comment: Please try using this CVS snapshot: http://snaps.php.net/php4-STABLE-latest.tar.gz For Windows: http://snaps.php.net/win32/php4-win32-STABLE-latest.zip And disable the Zend Optimizer.. Previous Comments: ------------------------------------------------------------------------ [2003-01-24 10:45:02] steveh@brendata.co.uk Any news? Is it worth trying this again on the latest CVS? ------------------------------------------------------------------------ [2003-01-07 07:17:19] nicos@php.net Opening it back then. ------------------------------------------------------------------------ [2003-01-07 07:14:36] steveh@brendata.co.uk This is still happening with php 4.3.0 and zend optimiser 2.0.3, I turned zlib.output_compression=on, tested and the downloaded file (a zip file) was corrupt, set zlib.output_compression=off and then the download worked fine. ------------------------------------------------------------------------ [2002-10-20 23:25:01] sniper@php.net No feedback was provided. The bug is being suspended because we assume that you are no longer experiencing the problem. If this is not the case and you are able to provide the information that was requested earlier, please do so and change the status of the bug back to "Open". Thank you. ------------------------------------------------------------------------ [2002-10-05 09:49:20] iliaa@php.net Please try using this CVS snapshot: http://snaps.php.net/php4-latest.tar.gz For Windows: http://snaps.php.net/win32/php4-win32-latest.zip I am unable to replicate the bug, it is more then likely that one of the recent changes in output handling code has resolved this issue. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/19436 -- Edit this bug report at http://bugs.php.net/?id=19436&edit=1

« previous php.bugs (#32977) next »