Re: [PHP-DEV] PHP Bug #17868: Multiple Includes
Michael D. Petersen [EMAIL PROTECTED] wrote... : I have been following PHP Bug #17868 for some time now (since upgrading to Red Hat 8.0 and Apache 2.0) with quite a bit of interest. This is the bug where multiple include statements don't work and only the first one gets parsed by PHP. Yes, only the first one gets parsed by all the subsequent get executed. This speeds the process up - what's the problem? -- Maxim Maletsky [EMAIL PROTECTED] -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] PHP Bug #17868: Multiple Includes
The problem is described in a little more detail here: http://bugs.php.net/bug.php?id=17868 Basically, if you have a document which has two or more include statements, each including a chunk of PHP code, only the first statement gets parsed by PHP. PHP is called everytime, but only the first statement gets executed as PHP code. All the rest just return the PHP code itself. For example: test.php: ?php printf(Hello!BR\n); ? test.shtml: First Include:BR !--#include virtual=test.php-- Second Include:BR !--#include virtual=test.php-- Requesting test.shtml via Apache 2 would return the following: First Include:BR Hello!BR Second Include:BR ?php printf(Hello!BR\n); ? The same thing happens even if the included PHP code is different each time -- only the first include gets parsed by PHP and the rest just return the code. This problem appeared with Apache 2 -- earlier versions would have parsed both include statements. Michael At 01:17 PM 1/20/2003 +0100, you wrote: Michael D. Petersen [EMAIL PROTECTED] wrote... : I have been following PHP Bug #17868 for some time now (since upgrading to Red Hat 8.0 and Apache 2.0) with quite a bit of interest. This is the bug where multiple include statements don't work and only the first one gets parsed by PHP. Yes, only the first one gets parsed by all the subsequent get executed. This speeds the process up - what's the problem? -- Maxim Maletsky [EMAIL PROTECTED] -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] PHP Bug #17868: Multiple Includes
--- Maxim Maletsky [EMAIL PROTECTED] wrote: Michael D. Petersen [EMAIL PROTECTED] wrote... : I have been following PHP Bug #17868 for some time now (since upgrading to Red Hat 8.0 and Apache 2.0) with quite a bit of interest. This is the bug where multiple include statements don't work and only the first one gets parsed by PHP. Yes, only the first one gets parsed by all the subsequent get executed. This speeds the process up - what's the problem? I think you misinterpreted the bug (unless I am instead), but Rasmus already responded that the problem lies with Apache 2's filters and that the Apache guys are well aware of the problems with that API. Chris -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] PHP Bug #17868: Multiple Includes
Seems to me like there's not much that can be done on the php side but more on the apache side. In the meantime I'd suggest migrating your server to Apache 1.3.27 until the problem is fixed since this may take quite a while. On Mon, 2003-01-20 at 09:28, Michael D. Petersen wrote: The problem is described in a little more detail here: http://bugs.php.net/bug.php?id=17868 -- Xavier Spriet [EMAIL PROTECTED] -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] PHP Bug #17868: Multiple Includes
Migrating back to Apache 1.3 is always a fallback solution. My main intent in mentioning this workaround was to get some feedback on what it may have inadvertantly broken, since commenting out the line of code seems to make Apache 2 work very well with PHP on my machine with no observable, negative side effects (yet). So, even though the apache2filter code is part of the PHP distribution, is it maintained by the Apache folks? Since the code in question (sapi_apache2.c) is part of the PHP distribution, I figured this (PHP-DEV) would be the correct forum, at least to start. Thanks for everyone's responses so far! Michael At 10:19 AM 1/20/2003 -0500, you wrote: Seems to me like there's not much that can be done on the php side but more on the apache side. In the meantime I'd suggest migrating your server to Apache 1.3.27 until the problem is fixed since this may take quite a while. On Mon, 2003-01-20 at 09:28, Michael D. Petersen wrote: The problem is described in a little more detail here: http://bugs.php.net/bug.php?id=17868 -- Xavier Spriet [EMAIL PROTECTED] -- 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
