Appreciate some help on this.
My Links and Files database hack ran into problems on a site using zlib.output_compression=on and php version 4.3.4. He got garbage on the screen, which was presumably compressed material not being uncompressed or vice versa.
The cryptic comment from his local expert was that
Quote:
In php.ini I changed the line
zlib.output_compression = On
to
zlib.output_compression = Off
Earlier when I was in there I had changed it too on (it was off). In the past I have found better performance from php websites having it on. If the website does zlib compression as well it can cause problems. Most sites check to see if php has it on to avoid the problem, but it seems the link software doesn't.
|
I seem to be in the minority - I am not taking any precautions, as they say...
How does one write a script that is safe against zlib.output_compression being "on"?