Tonymaestri Posted September 12, 2005 Posted September 12, 2005 Hi everybody!!! I didn't know where to post this topic, so I posted it here. Forgive me, but I am new to this Forum. Everytime I open my Forum homepage (http://bloggy.biz/board), I get this error: Warning: ob_start(): output handler 'ob_gzhandler' cannot be used after 'URL-Rewriter' in /home/MYUSERNAME/public_html/board/includes/page_header.php on line 44 When I refresh the page, the error disappears. We checked the page_header php file, but didn't find any mention of "URL-Rewriter"... as we are still experiencing trouble with Trojans and Viruses on our domain (problems which we trust will be solved soon... ), we'd like to know if this error might have something to do with it. We also checked the source code on the page, which reads: ><br /> <b>Warning</b>: ob_start(): output handler 'ob_gzhandler' cannot be used after 'URL-Rewriter' in <b>/home/MYUSERNAME/public_html/board/includes/page_header.php</b> on line <b>44</b><br /> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html dir="ltr"> <head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> <meta http-equiv="Content-Style-Type" content="text/css"> Of course I omitted my username in the code and in the error message. Any help with this? Thank you very much. Quote
TCH-Don Posted September 12, 2005 Posted September 12, 2005 Have you looked at the phpbb forum? I am not seeing the error when I go to your link. Quote
TweezerMan Posted September 13, 2005 Posted September 13, 2005 As near as I can tell by searching Google, this is a conflict between the use of gzip compression and transparent session IDs in PHP. The recommended solution is to add the following to your .htaccess file: >php_flag session.use_trans_sid off ...which will disable the use of transparent session IDs. Or, you could disable the use of gzip compression in your script (phpBB in this case). I see this error only when there is no PHPSESSID cookie stored on my machine (from www.bloggy.biz). When browsing to the page for the first time, I see the error, but the PHPSESSID cookie is also created, and subsequent views of the page do not display this error. If I delete the PHPSESSID cookie and visit the page again, I again see the error just for that one page (because the PHPSESSID cookie is recreated). Hope this helps... Quote
Tonymaestri Posted September 13, 2005 Author Posted September 13, 2005 As near as I can tell by searching Google, this is a conflict between the use of gzip compression and transparent session IDs in PHP. The recommended solution is to add the following to your .htaccess file: >php_flag session.use_trans_sid off ...which will disable the use of transparent session IDs. Or, you could disable the use of gzip compression in your script (phpBB in this case). I see this error only when there is no PHPSESSID cookie stored on my machine (from www.bloggy.biz). When browsing to the page for the first time, I see the error, but the PHPSESSID cookie is also created, and subsequent views of the page do not display this error. If I delete the PHPSESSID cookie and visit the page again, I again see the error just for that one page (because the PHPSESSID cookie is recreated). Hope this helps... <{POST_SNAPBACK}> Hey, thanks!!! This definitely helps. I have no idea what a transparent session ID is though... would that affect anything in the Forum functioning if we disable it? I think I'll wait until my wife logs in before doing anything... she's the one who knows about this stuff. I'm Black Cat's husband, anyway... please to meet you, David. Quote
TweezerMan Posted September 13, 2005 Posted September 13, 2005 With transparent session IDs enabled, PHP is able to silently rewrite relative URLs on your site to contain the PHP session ID. This is necessary only if cookies are not enabled in the user's browser to save the session ID in instead. Normally you wouldn't want the session ID to show up in URLs to your site because 1) they make your site URLs long and ugly, 2) they can mess up search engines trying to spider your forums, and 3) they can be a security risk. I've never run a phpBB forum and I don't have direct experience with this issue, so you should probably take what I've written here with a grain of salt. Your forums should be okay, but I can't be 100% sure or guarantee that they will. If this suggestion does not work out for you, it is easy enough to undo it though. I'm Black Cat's husband, anyway... please to meet you, David. Nice to meet you, Tony! Quote
Tonymaestri Posted September 13, 2005 Author Posted September 13, 2005 With transparent session IDs enabled, PHP is able to silently rewrite relative URLs on your site to contain the PHP session ID. This is necessary only if cookies are not enabled in the user's browser to save the session ID in instead. Normally you wouldn't want the session ID to show up in URLs to your site because 1) they make your site URLs long and ugly, 2) they can mess up search engines trying to spider your forums, and 3) they can be a security risk. I've never run a phpBB forum and I don't have direct experience with this issue, so you should probably take what I've written here with a grain of salt. Your forums should be okay, but I can't be 100% sure or guarantee that they will. If this suggestion does not work out for you, it is easy enough to undo it though. Nice to meet you, Tony! <{POST_SNAPBACK}> Ok, I got it now... it's that long sequence of numbers and letters that appear in the Forum URLs. If I understand right, disabling this might cause a problem with users who do not use cookies on their browser, which would then have to login again every time they open a Forum page. For the moment we have disabled gzip compression instead, and the error has gone away. Thanks. Quote
Blackcat Posted September 13, 2005 Posted September 13, 2005 For the moment we have disabled gzip compression instead, and the error has gone away. Thanks. <{POST_SNAPBACK}> Ehm... it's not exactly like this I first disabled GZip, then I decided to try to use the solution suggested by David (btw, thanks ) adding the line to .htm access. I have also tried loggin in as my test-user account, and everything works. Quote
TCH-Don Posted September 13, 2005 Posted September 13, 2005 Glad its all working. Way to go David Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.