Ron,
I agree that a bug report should be filed against zlib, but
unfortunately I don't know enough about the underlying issues to file
that report myself I do have enough context to file a new bug
against PHP but feel that bug #30153 does a great job of describing the
issue and believe it
Perhaps this is a stupid question, but has anyone ensured that zlib
rev 1.2.3 still exhibits this behavior? The trouble ticket is close
to useless for recapping this; but I'm happy to shepard a fix or some
solution through the zlib dev team.
The ticket indiciated that PHP is using it's own fork
My bad, I remembered the initial post wrong. Still, the primary bug report
should be for the zlib fellas. They're the ones who need to fix their lib.
Secondary, maybe php folks can see if the problem can be worked around. But
still, the guys with the real problem are the zlib guys. Have you filed a
