ID: 16023 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -Status: Open +Status: Bogus Bug Type: Apache related Operating System: Windows 2000 SP2 w/ all updates PHP Version: 4.1.2 New Comment:
Works fine for me. Maybe your browser (or a proxy) cached the page. Try shift-F5. Previous Comments: ------------------------------------------------------------------------ [2002-03-12 13:22:20] [EMAIL PROTECTED] Quick note: this is a minor issue, but thought it best to report it since others may be confused when they do the traditional <? phpinfo(); ?> script to test their setup. I have been running Apache for Windows v1.3.23 with PHP v4.1.1 (Apache module) as a service. All works well, with \WINNT\PHP.INI configured, PHP located in "\PHP". * Downloaded PHP v4.1.2 for Windows today (12Mar2002)...the .ZIP file. * Decompressed the .ZIP file. * Noted differences in php.ini-recommended vs. my current php.ini file (copied the cgi.* entries to my php.ini file, etc.). * Once ready, renamed my current "\PHP" directory to "\PHP v4.1.1", then renamed the decompressed directory from "\php-4.1.2-Win32" to "\PHP". Effectively swapped PHP 4.1.2 into place. * Shutdown Apache service, then started it again. * In webbrowser, loaded a php file containing ____________________ <?php phpinfo(); ?> ____________________ * Loading this webpage shows "PHP Version 4.1.1", NOT "PHP Version 4.1.2" as one might expect. * Using GRC.COM's ID Serve program, I get the following response: "Server: Apache/1.3.23 (Win32) PHP/4.1.3-dev" * Using NetCraft.com's "What's that site running?" feature, I get the following response: "Apache/1.3.23 (Win32) PHP/4.1.3-dev on Windows 2000" In a nutshell, it appears that the Apache for Windows PHP SAPI module is listing itself as both v4.1.1 and v4.1.3-dev, but NOT v4.1.2. Again, minor issue. But thought you should be aware, in case many people start contacting you about this. P.S. From the Command Prompt, if I enter 'php -v' in the \PHP directory, the CGI version accurately reports "4.1.2", so this issue may only involve the Apache SAPI module. I can't speak for any of the other SAPI modules. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=16023&edit=1
