Re: ob_gzhandler broken

Front page? If we put a notice for every bug we fix on the front page, it would be littered with stuff. Do you realize how many bugs are fixed (and new ones introduced most likely) in the current CVS tree? What makes this one so much more important than shuffle() being broken, the nasty SMP bug, the ODBC problems, pack memory leaks, the xbithack bogosity, strtotime problems, str_rot13 breakage, image corruption on certain browsers with output compression enabled, preg_split bug, ereg_replace crashes, bzopen crashes, array_rand thread safety problems, version_compare segfault, stripslashes crash, ldap resource problems, output buffering crashes, and about 20 more... It's a wonder this stuff works at all ;) -Rasmus On Thu, 22 Aug 2002, Brian Moon wrote: > Do you guys think that the users should be notified via a message on the > front page that ob_gzhandler does not work in the current versions and that > users should either upgrade (once fixed) or switch to > zlib.output_compression? > > Brian. > > ----- Original Message ----- > From: "Zeev Suraski" <zeev@zend.com> > To: "Brian Moon" <brian@phorum.org> > Cc: "Andreas Oesterhelt" <oes@oesterhelt.org>; <php-dev@lists.php.net> > Sent: Thursday, August 22, 2002 5:40 PM > Subject: Re: [PHP-DEV] ob_gzhandler broken > > > | Actually it's not that odd, looking at the source it appears that this is > | exactly what is 'supposed' to happen. I'll fix it. > | > | Zeev > | > | At 23:42 22/08/2002, Brian Moon wrote: > | >There are two mechanisms for compressing output in PHP. One is broke. > The > | >other works fine. > | > > | >You will see that phorum.org is now using the one that works. > | > > | >For the dev list: > | > > | >ob_gzhandler does do what this email says. zlib.output_compression does > | >not. i would submit this to the bug list, but it seems that there are > | >already several bugs about ob_gzhandler and that the general feeling is > that > | >it needs to be canned. > | > > | >Brian. > | >phorum.org > | > > | >----- Original Message ----- > | >From: "Andreas Oesterhelt" <oes@oesterhelt.org> > | >To: <brian@phorum.org> > | >Sent: Wednesday, August 21, 2002 3:21 PM > | >Subject: Phorum.org misconfigured? > | > > | > > | >| Hi Brian, > | >| > | >| ..cathy subject, eh? Sorry to trouble you with this: Being a developer > | >| of the soon-to-be-released Pivoxy HTTP proxy I stumbled accross a > problem > | >| our software is having with your (and other) sites and that I believe > | >| is a fault in those sites' PHP/Apache setups. > | >| > | >| Every HTTP request that carries the (completely legal!) HTTP header > | >| "Accept-Encoding: identity;q=1.0, *;q=0" is answered with a completely > | >| empty response. Same goes for "Accept-Encoding:". Both are legal ways > | >| to tell the server that we don't want the response compressed in any > | >| way. > | >| > | >| Since I failed to set up a server which has the same problem on my > | >| own machine, I would be *VERY* thankful if you could give tracing the > | >| problem at least a quick shot. > | >| > | >| For now, we'll just not send any Accept-Encoding: header at all, but, > | >| according to rfc2616, then "the server MAY assume that the client will > | >| accept any content coding." which is not what I want. > | >| > | >| I know that you are not responsible or authoritative for any flaws in > | >| PHP or apache, but as you seem to have experience with a major project > | >| in PHP, *and* run a site that is affected by the problem, I hope I > might > | >| raise your interest in the question. > | >| > | >| Your feedback will be very much appreciated. > | >| > | >| Best regards, > | >| --Andreas > | >| > | >| > | >| > | > > | > > | >-- > | >PHP Development Mailing List <http://www.php.net/> > | >To unsubscribe, visit: http://www.php.net/unsub.php > | > | > > > -- > PHP Development Mailing List <http://www.php.net/> > To unsubscribe, visit: http://www.php.net/unsub.php >