php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #603 CGI on WIN95 not working
Submitted: 1998-07-31 15:52 UTC Modified: 1998-08-13 16:37 UTC
From: Martin dot Krieger at fernuni-hagen dot de Assigned:
Status: Closed Package: Installation problem
PHP Version: 3.0.1 OS: Win95
Private report: No CVE-ID: None
View Developer Edit
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If you forgot your password, you can retrieve your password here.
Password:
Status:
Package:
Bug Type:
Summary:
From: Martin dot Krieger at fernuni-hagen dot de
New email:
PHP Version: OS:

 

 [1998-07-31 15:52 UTC] Martin dot Krieger at fernuni-hagen dot de 
The Manual says:
M> You can access php scripts simply by putting the php.exe
M> file into your scripts directory and using a url such
M> as: http://my.server/scripts/php.exe/page.php

With MS Personal Web Server on Win95 this does not work. Whatever I type for
'page.php' I always get a "No input file specified" message from PHP (3.01).
The method with the entries in the registry works, but I also want to try it
this way (for universal usage on all servers).

Another excerpt from the manual
M> The query information in an url after the question mark
M> (?) is passed as command line arguments to the
M> interpreter by the CGI interface. Usually interpreters
M> open and execute the file specified as the first
M> argument on the command line.
M>
M> When invoked as a CGI binary, PHP refuses to interpret
M> the command line arguments

As opposit to this statement a
http://localhost/Scripts/php.exe?/autoexec.bat 'works' on my machine. Bug or
feature?

Greetings from Cologne, Germany

  Martin

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [1998-08-13 16:37 UTC] shane 
The manual was probably right at some point.  Anyway, you shouldnt place any language parser in any cgi (or script) directory.  It's generaly thought of as unsafe :)  Irregardless, neither ways work for me, nor does it bother me that it doesnt (for the above reason).  Any decent server should have some way of letting you set the parser outside the server tree, and use just /www.com/page.php

The documentation should be fixed.
 
PHP Copyright © 2001-2026 The PHP Group
All rights reserved. 		Last updated: Mon Jan 05 02:00:02 2026 UTC