ID: 20779 User updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Duplicate -Bug Type: Apache related +Bug Type: *Configuration Issues Operating System: Win2k Pro PHP Version: 4.2.3 New Comment:
Error with Version in header of posting ... Version of PHP is 4.2.3. Previous Comments: ------------------------------------------------------------------------ [2002-12-03 00:02:51] [EMAIL PROTECTED] Error with Version in header of posting ... Version of PHP is 4.2.3. ------------------------------------------------------------------------ [2002-12-02 23:56:10] [EMAIL PROTECTED] Hi there Additional Category: Apache Just to clarify some points, i am using Apache 2.0.43 not Apache 2.0.39. So does the warning (below), of which I was aware of apply to newer versions of Apache (ie 2.0.40 and later). If its a known issue, then what measure have been taken to fix it. I believe its a PHP error. Apache runs everything else okay. The apache server environment is only for local development (i.e desktop). Secondly, I am using 4.2.3, which I downloaded on Saturday, Australian DST. Charlie PS The documentated warning about PHP and apache on windows for sapi seem to contradictory .... comapre these two sentences: "PHP 4.2.3 its known to work in conjunction with Apache 2.0.39." --- so PHP 4.2.3 works. "We do not recommend to use PHP 4.2.3 along with Apache 2.0.39." --- so as it works, it is not recommened. Eh? "Don't try to use this version of PHP with any other version of Apache." --- Is that earlier (older) or later (newer) versions of apache i.e before/after v.2.0.39. A fuller explaination would be preferable. I know that a the PHP 4.2.2 sapi worked with Apache 2.0.39, via console set up (not as a service) - although it was fiddley and a manual start up - but no errors. ------------------------------------------------------------------------ [2002-12-02 23:55:34] [EMAIL PROTECTED] Hi there Additional Category: Apache Just to clarify some points, i am using Apache 2.0.43 not Apache 2.0.39. So does the warning (below), of which I was aware of apply to newer versions of Apache (ie 2.0.40 and later). If its a known issue, then what measure have been taken to fix it. I believe its a PHP error. Apache runs everything else okay. The apache server environment is only for local development (i.e desktop). Secondly, I am using 4.2.3, which I downloaded on Saturday, Australian DST. Charlie PS The documentated warning about PHP and apache on windows for sapi seem to contradictory .... comapre these two sentences: "PHP 4.2.3 its known to work in conjunction with Apache 2.0.39." --- so PHP 4.2.3 works. "We do not recommend to use PHP 4.2.3 along with Apache 2.0.39." --- so as it works, it is not recommened. Eh? "Don't try to use this version of PHP with any other version of Apache." --- Is that earlier (older) or later (newer) versions of apache i.e before/after v.2.0.39. A fuller explaination would be preferable. I know that a the PHP 4.2.2 sapi worked with Apache 2.0.39, via console set up (not as a service) - although it was fiddley and a manual start up - but no errors. ------------------------------------------------------------------------ [2002-12-02 21:41:43] [EMAIL PROTECTED] >From the docs: ---- http://www.php.net/manual/en/printwn/install.apache2.php ---- Note: Apache 2.0 SAPI-support started with PHP 4.2.0. PHP 4.2.3 its known to work in conjunction with Apache 2.0.39. Don't try to use this version of PHP with any other version of Apache. We do not recommend to use PHP 4.2.3 along with Apache 2.0.39. ---- And btw, are you trying 4.2.3 or 4.3.0RC2, you list both in this bug report. This looks like an Apache2 related bug so the category may want to reflect that but I personally have no idea so won't touch it :) ------------------------------------------------------------------------ [2002-12-02 21:28:38] [EMAIL PROTECTED] Please excuse the spelling mistake : dynamic link librart should be dynamic link library. ------------------------------------------------------------------------ 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/20779 -- Edit this bug report at http://bugs.php.net/?id=20779&edit=1
