This is correct for Apache and probably NES too. There are other servers that do this though. I posed the question to an apache newsgroup and the answer was that it isn't any less efficient to open and print the file in perl. I guess convenience isn't high on their list of priorities. What I ended up doing was write a "perl-side-include" sub that performs the substitution wherever a <!--#include...> tag was found.
-- Mark Thomas [EMAIL PROTECTED] Sr. Internet Architect User Technology Associates, Inc. $_=q;KvtuyboopuifeyQQfeemyibdlfee;; y.e.s. ;y+B-x+A-w+s; ;y;y; ;;print;; > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] > Sent: Friday, December 07, 2001 1:00 PM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: [Perl-unix-users] Server-Side Includes in Perl Scripts > > > Our web administrator just told me that... > > "Web servers don't parse the output of CGI scripts for SSIs." > > after I asked her... > > "My perl script contains server-side include statements. Will > these work > with a cgi extension?" > > Is this true? I would like the server-side include > statements to be parsed > after the perl engine parses the script? > > We are running Netscape Enterprise Web Server. > > Gregory J Toland > Sr. Systems Architect > CHM, Inc. > (301) 457-8058 > [EMAIL PROTECTED] > > _______________________________________________ > Perl-Unix-Users mailing list. To unsubscribe go to > http://listserv.ActiveState.com/mailman/subscribe/perl-unix-users > _______________________________________________ Perl-Unix-Users mailing list. To unsubscribe go to http://listserv.ActiveState.com/mailman/subscribe/perl-unix-users
