Bug #19919

"output handler 'ob_gzhandler' cannot be used after 'URL-Rewriter'" on backend login

Added by Carsten Pohle over 4 years ago. Updated over 2 years ago.

Status:Accepted Start date:2009-01-26
Priority:Should have Due date:
Assignee:Oliver Hader % Done:

0%

Category:-
Target version:-
TYPO3 Version:4.2 Complexity:
PHP Version:5.2
Votes: 0

Description

On the backend login-screen, the message

Warning: ob_start() [ref.outcontrol]: output handler 'ob_gzhandler' cannot be used after 'URL-Rewriter' in /PATH_TO_TYPO3_INSTALL/typo3/init.php on line 389

appears.

Fix: Move the "compression" block befor the "BackEnd User authentication".

(issue imported from #M10273)

bug_0010273.diff (1 kB) Administrator Admin, 2009-01-26 16:02


Related issues

duplicated by Core - Bug #21804: output handler 'ob_gzhandler' cannot be used after 'URL-R... Resolved 2009-12-05

History

Updated by Oliver Hader about 4 years ago

I can confirm this issue on a website running at Domainfactory...
Please tell whether you have phpMyAdmin installed and in what version.
Please also look into the headers sent back to the client and look for "Transfer-Encoding".
Thanks!

Updated by Peter Kraume about 4 years ago

I can confirm this problem with Domainfactory and PMA 4.2.0 / PMA 4.3.0.
After uninstalling PMA the problem is gone.

Updated by Steffen Gebert about 4 years ago

I can reproduce it on one site using 4.3-dev
not reproducable on another site running 4.2.6, but also with BE-compression enabled.
Both on dF-servers.

Could you find out anything more about this bug? Is PMA responsible for it or does this TYPO3 bug only caused by PMA?

Updated by Tobias H. over 3 years ago

I have the same error, with 4.3 now logged:

Core: Error handler (BE): PHP Warning: ob_start() [ref.outcontrol]: output handler 'ob_gzhandler' cannot be used after 'URL-Rewriter' in /../typo3_src-4.3.0/typo3/init.php line

I have this error only when the PMA is installed. Of course the newest version.

Updated by Steffen Gebert about 3 years ago

This one is still valid, does anyone have an idea?

Tobias, are you also at domainfactory?

Don't know if it's a good idea to move the compression block around.

Updated by Peter Kraume over 2 years ago

Any news on this issue?

Updated by Oliver Hader over 2 years ago

Can somebody using Domainfactory please post the "zlib.*" part of the php.ini? I guess that compression is already enabled/defined there - thus, checking in TYPO3 if compression is already enabled should be enough.

Updated by Steffen Gebert over 2 years ago

Settings are
zlib.output_compression Off Off
zlib.output_compression_level -1 -1
zlib.output_handler no value no value

Updated by Steffen Gebert over 2 years ago

Searching the web shows we're not alone..

I found a PHP bug from back in 2003, when this error message was introduced: http://bugs.php.net/24315

PHP now (latest stable CVS) reports the correct error message (ob_start(): output handler 'ob_gzhandler' cannot be used after 'URL-Rewriter') if you call ob_start('ob_gzhandler'); after session_start hs been called and trans_sid is used. The solution is to call ob_start('ob_gzhandler'); before session_start().

Updated by Steffen Gebert over 2 years ago

In EXT:phpmyadmin/res/phpMyAdmin-xxx/libraries/session.inc.php I see the following lines:

// but not all user allow cookies
@ini_set('session.use_only_cookies', false);
@ini_set('session.use_trans_sid', true);
@ini_set('url_rewriter.tags', 'a=href' ...)

As we 'can' cookies, I suggest to just remove these ini_set().
As adviced, session_start() is called afterwards, but I think TYPO3 itself already started a session.

Can sb. have a quick check on deactivating these lines, please?

Updated by Steffen Gebert over 2 years ago

Doesn't work..

Also available in: Atom PDF