ID: 16601
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Feedback
Bug Type: Dynamic loading
Operating System: Windows 2000
PHP Version: 4.2.0RC4
New Comment:
The 'expose_php' header also appears in the regular page output for
phpinfo() when there's an error popup.
X-Powered-By: PHP/4.2.0RC4 Content-type: text/html
Previous Comments:
------------------------------------------------------------------------
[2002-04-14 19:45:33] [EMAIL PROTECTED]
I went on a limb and rebooted. No change. Errors remain.
------------------------------------------------------------------------
[2002-04-14 19:38:08] [EMAIL PROTECTED]
It's a CGI to Apache 1.3.22.
I have php4ts.dll in two places according to a windows file search,
C:\winnt and c:\winnt\system32. I tried also keeping it with php.exe
and tried without. Same result.
------------------------------------------------------------------------
[2002-04-14 19:25:33] [EMAIL PROTECTED]
Are you running PHP as CGI or some webserver module?
And if the latter, which webserver and version?
Are you sure you have really replaced the correct php4ts.dll? And that
you don't have some older one laying
around somewhere? Tried booting yet? :)
------------------------------------------------------------------------
[2002-04-14 19:18:46] [EMAIL PROTECTED]
I'm not sure if it helps, but I click the OK button for the error
message on a phpinfo() page once for php_bz2.dll, once for
php_interbase.dll, and once for php_mssql.dll, then I have to go again
for another round of clicking OK, but with clicking twice for each
extension.
------------------------------------------------------------------------
[2002-04-14 19:10:01] [EMAIL PROTECTED]
It is from the same package and I did replace the old 4.1.1 php4ts.dll
with the one in the 4.2.0RC4 package. ctype, db, dbase, dbx, filepro,
hyperwave, mbstring, shmop, sockets, tokenizer, and w32api are the ones
that load without error.
------------------------------------------------------------------------
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/16601
--
Edit this bug report at http://bugs.php.net/?id=16601&edit=1
