It was a misconfiguration. I took a look and cleaned it up a bit from this:
AddEncoding application/x-xsp xsp PerlModule AxKit AxAddProcessor application/x-xsp . AxAddStyleMap application/x-xsp Apache::AxKit::Language::XSP AxAddStyleMap text/xsl Apache::AxKit::Language::LibXSLT AxAddXSPTaglib AxKit::XSP::ESQL AxAddXSPTaglib AxKit::XSP::Util AxAddXSPTaglib AxKit::XSP::Sendmail AxAddXSPTaglib AxKit::XSP::Param AxAddXSPTaglib AxKit::XSP::Exception AxAddXSPTaglib AxKit::XSP::PerForm AxAddXSPTaglib AxKit::XSP::WebUtils AxAddPlugin Apache::AxKit::Plugins::QueryStringCache AxCacheDir /tmp/axkit <Location "/xml"> SetHandler perl-script PerlHandler AxKit </Location> <Location "/cgi-bin/xsp"> SetHandler perl-script PerlHandler AxKit </Location> <Location "/cgi-bin/xsp"> SetHandler perl-script PerlHandler AxKit #AxAddProcessor text/xsl /cgi-bin/xsp/modules.xsl </Location> <Location "/cgi-bin/xsp/tisch"> SetHandler perl-script PerlHandler AxKit AxAddProcessor text/xsl /cgi-bin/xsp/tisch/style/basic.xsl </Location> <Files *.xsp> AxAddProcessor application/x-xsp . </Files> to this: AddEncoding application/x-xsp xsp PerlModule AxKit AxAddStyleMap application/x-xsp Apache::AxKit::Language::XSP AxAddStyleMap text/xsl Apache::AxKit::Language::LibXSLT AxAddXSPTaglib AxKit::XSP::ESQL AxAddXSPTaglib AxKit::XSP::Util AxAddXSPTaglib AxKit::XSP::Sendmail AxAddXSPTaglib AxKit::XSP::Param AxAddXSPTaglib AxKit::XSP::Exception AxAddXSPTaglib AxKit::XSP::PerForm <Location "/cgi-bin/xsp"> SetHandler perl-script PerlHandler AxKit SetHandler axkit AxAddProcessor text/xsl /cgi-bin/xsp/tisch/style/basic.xsl </Location> <Files *.xsp> AxAddProcessor application/x-xsp . </Files> Both use a little bit in .htaccess files, but only for turning on debug and setting cache location(should be moved into httpd.conf). What is it that caused the strange behavior. The only thing that I can see is that maybe it had something to do with 2 different instances of AxAddProcessor application/x-xsp . Sorry to waste so much time on this. I should have looked at my config more closely at first. I did learn quite a bit though :) Andy Matt Sergeant wrote: > On Tue, 19 Feb 2002, Andrew Parker wrote: > > >>Oh, well, it was worth a try. It seemed sensible because what is >>sitting in the cache is the generated XML. It seems like whenever it >>wants to rerun the XSP it will have to recompile it as well. >> > > No, that cache you're looking at is the code cache - the XSP page is > compiled into a Perl module, which needs to be cached in memory. If you > recompile it on every hit you lose all the performance. > > It still gets *executed* on every hit. > > >>Could the whole thing be caused by a misconfiguration? I could send you >>my httpd.conf if that will help. >> > > Just the relevant AxKit parts - not the whole thing. > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
