ID: 20864
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
-Status: Open
+Status: Feedback
Bug Type: Mail related
Operating System: Windows 2000
PHP Version: 4.2.3
New Comment:
Are you sure your php.ini is even read? Is it in correct place? Is it
with correct NAME..(common problem, people tend to name it php.ini.ini
on Windows)
Previous Comments:
------------------------------------------------------------------------
[2002-12-07 10:10:43] [EMAIL PROTECTED]
I seem to have been misunderstood. I tried using the referred devel
snapshot and I always get the "PHP CGI cannot
be accessed directly [...]" message, even with the parameters shown
above. Can anybody tell me what else might be wrong (note: I haven't
had these problems with any other PHP release before..)
------------------------------------------------------------------------
[2002-12-07 02:55:26] [EMAIL PROTECTED]
In my case, Cc: and Bcc: work now (dev and stable snapshots on winXP).
Christoph
------------------------------------------------------------------------
[2002-12-06 18:31:06] [EMAIL PROTECTED]
So does the mail work now?
------------------------------------------------------------------------
[2002-12-06 12:35:48] [EMAIL PROTECTED]
Addendum to last comment: php-cgi.exe does not make the request hang
forever. Sorry about that. All the other info still stands.
------------------------------------------------------------------------
[2002-12-06 12:32:27] [EMAIL PROTECTED]
I'm having a hard time getting that CVS build to work (using IIS) ...
I'm using it as a CGI binary and it always returns the "PHP CGI cannot
be accessed directly blabla" page. Here are my php.ini CGI options:
cgi.force_redirect = 0;
cgi.redirect_status_env = ;
fastcgi.impersonate = 1;
cgi.rfc2616_headers = 1;
I've tried mapping the .php extension to both php.exe and php-cgi.exe.
Mapping it to php-cgi.exe seems to make the request for any script hang
around forever.
By the way, it would be nice if the CVS Windows builds didn't have Unix
linebreaks on the text/ini files :)
------------------------------------------------------------------------
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/20864
--
Edit this bug report at http://bugs.php.net/?id=20864&edit=1
