You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apache-bugdb@apache.org by Marc Slemko <ma...@znep.com> on 1998/09/21 05:30:01 UTC

Re: os-windows/3034: cannot get CGI to execute correctly on Windows 95 with version 1.3.1 (fwd)

The following reply was made to PR os-windows/3034; it has been noted by GNATS.

From: Marc Slemko <ma...@znep.com>
To: apbugs@apache.org
Cc:  Subject: Re: os-windows/3034: cannot get CGI to execute correctly on
 Windows 95 with version 1.3.1 (fwd)
Date: Sun, 20 Sep 1998 20:27:01 -0700 (PDT)

 ---------- Forwarded message ----------
 Date: Sun, 20 Sep 1998 20:27:59 -0700
 From: Glen Plantz <pl...@fgm.com>
 To: marc@apache.org,
     plantz@fgm.com
 Subject: Re: os-windows/3034: cannot get CGI to execute correctly on Windows 95
     with version 1.3.1
 
 Marc,
     Thanks for the quick response. I do have the "#! " in the first line of the
 cgi script, as required. However, I _do_ have spaces in the directories pointing
 to the cgi script.   Thanks so much for the tip; I look forward to getting the new
 1.3.2....
 
     Thanks again for responding so quickly!
 
             Glen
 
 marc@apache.org wrote:
 
 > [In order for any reply to be added to the PR database, ]
 > [you need to include <ap...@Apache.Org> in the Cc line ]
 > [and leave the subject line UNCHANGED.  This is not done]
 > [automatically because of the potential for mail loops. ]
 > [If you do not include this Cc, your reply may be ig-   ]
 > [nored unless you are responding to an explicit request ]
 > [from a developer.                                      ]
 > [Reply only with text; DO NOT SEND ATTACHMENTS!         ]
 >
 > Synopsis: cannot get CGI to execute correctly on Windows 95 with version 1.3.1
 >
 > State-Changed-From-To: open-closed
 > State-Changed-By: marc
 > State-Changed-When: Sun Sep 20 15:21:33 PDT 1998
 > State-Changed-Why:
 > First, be aware that interpreted CGIs have to have a
 > #! line as the first line specifying the name of the
 > interpreter.
 >
 > Second, in 1.3.1 there is a bug related to directories
 > with spaces in the name.  This is fixed in 1.3.2, which
 > should be available this week.