The following reply was made to PR mod_include/2755; it has been noted by GNATS.

From: Marc Slemko <[EMAIL PROTECTED]>
To: Federico Giannici <[EMAIL PROTECTED]>
Cc: Apache bugs database <[EMAIL PROTECTED]>
Subject: Re: mod_include/2755: #exec cmd doesn't work
Date: Tue, 4 Aug 1998 01:22:16 -0700 (PDT)

 On Sun, 2 Aug 1998, Federico Giannici wrote:
 
 > [EMAIL PROTECTED] wrote:
 > > 
 > > Synopsis: #exec cmd doesn't work
 > > 
 > > State-Changed-From-To: open-feedback
 > > State-Changed-By: marc
 > > State-Changed-When: Sat Aug  1 11:07:59 PDT 1998
 > > State-Changed-Why:
 > > It works just fine for me.
 > > 
 > > Do other SSI directives work in the same page?
 > 
 > Yes, if I change the "cmd" with a "cgi" (changing path to url) it
 > works...
 > 
 > The problem is that i decided to use cmd because I have to pass some
 > arguments to the script.
 > I tried to pass the arguments to the cgi in the normal URL form (with a
 > "?"), but it didn't worked. Is is normal? Is there another way?
 
 See the docs; use "include virtual" if you want to execute something with
 a query string or path info.
 
 > 
 > > If you look at the source of the page generated, does it
 > > still contain the SSI directives unparsed?
 > 
 > No, and it doesn't contain any error or any output, completly nothing!
 
 Are you sure you are viewing the source and not the parsed HTML?
 
 > And no error is logged!
 > 
 > > Give an example of an exec cmd you are trying to use.
 > 
 > I tried with many different commands, even a simple shell script with
 > only a "echo hello". I tried to put it in many different directory, also
 > in current. I chmoded them 777...
 > No result at all!!!
 
 Again, please give an example.  An exact example of what you are putting
 in your file that you think should be parsed.
 

Reply via email to