Very Computer

hello,

Thanks for all the help on my last apache question (about running it as root).

Now I have another problem...we are changing over from the CERN server.
Since CERN does not do SSI, someone here wrote a perl script to fake it.

The perl script, in conjunction with CERN, allows SSI calls of the form:

<!--#exec cgi="/cgi-bin/my_cgi/foo/bar" -->    

(where my_cgi is the actual cgi script)

and passes along the path information to the CGI as one would expect.

Apache 0.8.14, however, gets confused with the above call. It does not allow
passing path information in this manner.

I suspect that Apache is right (compliant with the spec) while our other
system is not. So, I need to know the proper way to do what we were doing
before.

How do I pass information (args) to a CGI script in a server-side-include
using the exec cgi call?

Also, is there a way to disallow exec cmd calls while still allowing
exec cgi calls?

thank you for your time,

Dwayne Fontenot

not yet.

Quote:>...
>Now I have another problem...we are changing over from the CERN server.
>Since CERN does not do SSI, someone here wrote a perl script to fake it.

>The perl script, in conjunction with CERN, allows SSI calls of the form:

><!--#exec cgi="/cgi-bin/my_cgi/foo/bar" -->

>(where my_cgi is the actual cgi script)

>and passes along the path information to the CGI as one would expect.

>Apache 0.8.14, however, gets confused with the above call. It does not allow
>passing path information in this manner.

>I suspect that Apache is right (compliant with the spec) while our other
>system is not. So, I need to know the proper way to do what we were doing
>before.

>How do I pass information (args) to a CGI script in a server-side-include
>using the exec cgi call?

Apache is compatible with the NCSA 1.3 behaviour in this respect.
However, you can do what you want with apache:

<!--#include virtual="/cgi-bin/my_cgi/foo/bar" -->

Quote:>Also, is there a way to disallow exec cmd calls while still allowing
>exec cgi calls?

Not yet; but there may be in a future version.