The following reply was made to PR mod_include/5799; it has been noted by GNATS.
From: Marc Slemko <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: mod_include/5799: Server Side Includes of CGI with passed parameters fails with [an error occurred while processing this directive] Date: Tue, 22 Feb 2000 14:19:32 -0700 (MST) On 22 Feb 2000, Don O'Neil wrote: > >Description: > When using mod_include to execute a cgi in a .shtml page with the following > content: > > <html> > <!--#exec cgi="/cgi/env.cgi?name=Don"--> > </html> > > The following error is generated at the browser: > [an error occurred while processing this directive] > > The follwing entry is generated in the log file: > invalid CGI ref "/cgi/env.cgi?name=Don" in > /www/amplespace/public_html/test/index.shtml > > When you execute the same shtml without the passed parameter everything > works fine.. ie: > > <html> > <!--#exec cgi="/cgi/env.cgi"--> > </html> > > Using #include virtual is a work around, but is not really appropriate. This isn't a bug. That is the way things work. "exec cgi" takes the file named and executes it as a CGI. It passes any query string from the original page. That is the way SSIs were originally created, and Apache follows that. Since it makes little sense, however, to have special cases for CGIs, Apache offers "include virtual" which takes any URI on the server (could be a CGI, a file, a module, etc.) and handles it without the odd semantics that exec cgi has.
