Hi,

   I sent out an email yesterday describing some problems that I'm having
   with Apache::SSI.  I've narrowed things down significantly and hope that
   this extra info can help someone point me in the right direction.

   Basically, it all boils down to the fact that once an SSI directive
   with #EXEC CGI is parsed, the document fails to parse any further
   SSI directives *if the script to be executed has a perl-script 
   handler.*

   If I put the lines

      print q(<!--#EXEC CGI="/perl/navbar.pl" -->), "\n";
      print q(<!--#EXEC CGI="/perl/navbar.pl" -->), "\n";

   at the top of my perl script, the first SSI gets parsed.  If it points
   to another include file that has lots of sub-levels, each with their own
   CGI scripts, they're all run fine.  It just stops parsing once it finishes
   with the first one.

   The files that are being included are handled like so:

      <Location /perl/>
         SetHandler perl-script
         PerlModule Apache::Registry
         PerlHandler Apache::Registry
      </Location>

   They're included from other HTML and CGI scripts via SSI without problems.

   But if I have a script handled by mod_perl, configured like

      <Files *.pl>
         SetHandler perl-script
         PerlModule Apache::OutputChain Apache::SSIChain Apache::Registry
         PerlHandler Apache::OutputChain Apache::SSIChain Apache::Registry
      </Files>

   with two SSI directives like I first listed above, only the first is
   parsed.

   What do I need to do?  I've tried Apache::Filter with the same results, 
   so I'm guessing that I missed an important step at a more basic level.
   Please, help!

Thanks,

Chris
`


-- 
Reporting bugs: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html

Reply via email to