#22698 [Com]: 'ob_gzhandler' cannot be used twice: still present in 4.3.1 when using sessions

ID: 22698 Comment by: voided at deviantnewmedia dot com Reported By: bilo at mit dot it Status: Open Bug Type: Session related Operating System: Linux PHP Version: 4.3.1 New Comment: ok it looks like the scripts make use of: ob_start('ob_gzhandler'); and since it is already included in php.ini it gives out the error seen previously... Previous Comments: ------------------------------------------------------------------------ [2003-04-14 13:39:44] voided at deviantnewmedia dot com same here with horde/imp. turned off session.use_trans_sid and i am getting : Warning: (null)() [ref.outcontrol]: output handler 'ob_gzhandler' cannot be used twice in Unknown on line 0 ------------------------------------------------------------------------ [2003-04-08 20:54:51] dave at toad dot net For what it's worth, I have session.use_trans_sid = 0 and I am getting: [Tue Apr 8 21:48:31 2003] [error] PHP Warning: (null)() [<a href='http://www.php.net/ref.outcontrol'>ref.outcontrol</a>]: o utput handler 'ob_gzhandler' cannot be used twice in Unknown on line 0 This is with current horde/imp; I am not aware that the ob_gzhandler is being invoked anyplace in particular. ------------------------------------------------------------------------ [2003-03-17 03:59:33] bilo at mit dot it Yes it did, thank you. ------------------------------------------------------------------------ [2003-03-14 11:13:09] sniper@php.net So did it 'fix' this problem or not? ------------------------------------------------------------------------ [2003-03-14 10:34:24] bilo at mit dot it Ok. I'll try. BTW ... Why? And what does setting this parameter to off changes for me in the way I write scripts and pages ? I see that a cookie with PHPSESSID is still sent. Does this mean that I have to add "&PHPSESSID=xxxxxxx" to each URI when cookies are not available? ------------------------------------------------------------------------ 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/22698 -- Edit this bug report at http://bugs.php.net/?id=22698&edit=1