Very Computer

Sometimes things work exactly opposite as you think they would. Here's
a good example.

When trying to include a call to a cgi script via SSI the following
difference between Netscape 3.6 and Apache web servers crops up.

In Netscape, CGIs can only be processed via the "exec command".
Therefore, the correct format for the Netscape webserver is the
following:

<!--#exec cgi="/cgi-bin/techadv/techPromo.cgi?id=proj&level=0" -->

However, it is the opposite method for  Apache webservers. Apache
webservers uses the following format:

<!--#include virtual="/cgi-bin/techadv/techPromo.cgi?id=proj&level=0"
-->

Thanks to Patrice Jones for her help.

Quote:> Sometimes things work exactly opposite as you think they would. Here's
> a good example.

> When trying to include a call to a cgi script via SSI the following
> difference between Netscape 3.6 and Apache web servers crops up.

> In Netscape, CGIs can only be processed via the "exec command".
> Therefore, the correct format for the Netscape webserver is the
> following:

><!--#exec cgi="/cgi-bin/techadv/techPromo.cgi?id=proj&level=0" -->

> However, it is the opposite method for  Apache webservers. Apache
> webservers uses the following format:

><!--#include virtual="/cgi-bin/techadv/techPromo.cgi?id=proj&level=0"
> -->

You can use #exec cgi for Apache, but then the only query string the CGI
would see would be one on the URL of the SSI page.  Without any query
string, #exec cgi works the same for either.

SSI is server specific, for example IIS might do some things different
from either of these.  That is why you need to read docs for the server
being used.  However, during the period of time my ISP was using the
Netscape server, I did not have a clue where to find docs for it without
buying the server.

--
David Efflandt - All spam ignored  http://www.de-srv.com/
http://www.autox.chicago.il.us/  http://www.berniesfloral.net/
http://cgi-help.virtualave.net/  http://hammer.prohosting.com/~cgi-wiz/