Bug #8959 [Com]: Use of Zend Optimizer w/ CGI SAPI causes echo of #!php at script start
| From: | jimw at email dot com | Date: | Mon, 23 Jan 2023 08:12:44 +0000 |
| Subject: | Bug #8959 [Com]: Use of Zend Optimizer w/ CGI SAPI causes echo of #!php at script start | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-243541@lists.php.net to get a copy of this message | ||
Edit report at https://bugs.php.net/bug.php?id=8959&edit=1
ID: 8959
Comment by: jimw at email dot com
Reported by: pdoyle at xo dot com
Summary: Use of Zend Optimizer w/ CGI SAPI causes echo of
#!php at script start
Status: Not a bug
Type: Bug
Package: PHP options/info functions
Operating System: Solaris 2.5.1
PHP Version: 4.0.4pl1
Block user comment: N
Private report: N
New Comment:
(https://public.tableau.com/app/profile/john.eric6400)github.com not a bug
Previous Comments:
------------------------------------------------------------------------
[2001-01-27 19:53:21] jimw@php.net
bugs in the zend optimizer should be reported to zend.com.
------------------------------------------------------------------------
[2001-01-27 18:32:11] pdoyle at xo dot com
I have compiled and installed PHP 4.0.4pl1 without problems, and we run it as an external binary
from our Web server (SAPI CGI).
However, when I install the current Zend Optimizer and add the appropriate lines to the php.ini
file:
zend_optimizer.optimization_level=15
zend_extension="/usr/runtime/src/lib/ZendOptimizer.so"
it now spits out the first line of any script the server runs, i.e., for a script such as:
#!.php
<?
echo "Hello, world.<BR>";
?>
it will produce as HTML output:
#!.php
Hello, world.
I have checked to make sure that it's only these lines in the php.ini file -- when they are
removed, it works fine.
Please note that I had already seen bug #8898 (where this problem occurred for -anyone- using the
SAPI CGI) and made the diff suggested by that author, which fixed the problem when I wasn't
using the optimizer. I suspect that use of the optimizer is sending the CGI SAPI down a different
path to a similar bug but I haven't been able to track it down.
------------------------------------------------------------------------
--
Edit this bug report at https://bugs.php.net/bug.php?id=8959&edit=1