php-windows Digest 6 Jul 2002 15:46:45 -0000 Issue 1227
Topics (messages 14571 through 14572):
WinampCOM problem
14571 by: Olivier Hubert
Problems installing PHP4 under PWS
14572 by: Alex Francis
Administrivia:
To subscribe to the digest, e-mail:
[EMAIL PROTECTED]
To unsubscribe from the digest, e-mail:
[EMAIL PROTECTED]
To post to the list, e-mail:
[EMAIL PROTECTED]
----------------------------------------------------------------------
--- Begin Message ---
Hiya,
Just wondering if anyone else is having this problem. I am trying to
control Winamp through HTTP using the WinampCOM plugin. It works fine when
I call the script from the command line but not at all when the exact same
script runs through HTTP (using Apache). Here is a bit of the code I use:
$Winamp = new COM("WinampCOM.Application") or die('Could not
instanciate the WinampCOM object');
if (isset($Winamp))
echo 'Test: ' . $Winamp->CurrentSongFileName();
else
echo 'Not working';
Now, through the command line I see 'Test: ' followed by the current song's
name but on the web page I see only 'Test: '. Anyone ever experienced this?
Any help appreciated. For those who wonder, WinampCOM is available at:
http://www.adcock8.freeserve.co.uk/winamp.htm.
Thanks,
Olivier
--- End Message ---
--- Begin Message ---
I have installed PHP4 under PWS and when I test using the command prompt it
seems to work alright. However when I try to run a test php script through
the browser I get the following error:
"Security Alert! PHP CGI cannot be accessed directly.
This PHP CGI binary was compiled with force-cgi-redirect enabled. This
means that a page will only be served up if the REDIRECT_STATUS CGI
variable is set. This variable is set, for example, by Apache's Action
directive redirect.
You may disable this restriction by recompiling the PHP binary with the
--disable-force-cgi-redirect switch. If you do this and you have your PHP
CGI binary accessible somewhere in your web tree, people will be able to
circumvent .htaccess security by loading files through the PHP parser. A
good way around this is to define doc_root in your php.ini file to
something other than your top-level DOCUMENT_ROOT. This way you can
separate the part of your web space which uses PHP from the normal part
using .htaccess security. If you do not have any .htaccess restrictions
anywhere on your site you can leave doc_root undefined. If you are running
IIS, you may safely set cgi.force_redirect=0 in php.ini."
I have tried setting cgi.force_redirect=0 and it makes no difference.
I have also installed apache, but am not sure if I need to remove PWS to use
it.
--
Alex Francis
--- End Message ---
