> <Location /> > PerlSetVar SessionTable WF_PUBLIC_SESSSION > PerlSetVar SessionArea xxxxxxx > PerlSetVar SessionTimeout +20m > PerlInitHandler ITAS::Handler::Session > PerlHandler ITAS::Handler::Mason > </Location>
you can get the same effect putting all of that stuff on a per-server level (in other words, outside of any <Location|Directory|etc> container. > > <LocationMatch ^/(script|image|picture)/> > SetHandler default-handler > </LocationMatch> > > > The 'PerlInitHandler' is also called while calling the second location for > static output ^/(script|image|picture)/. How can I stop that? Or even > better stop any handler in that location at all? in general, if you have this criterion then you want to place the PerlInitHandler inside of only the containers you want to handle, and leave it out of the rest. this is the approach that most people take. if you really want to undo the configuration for a specific container you would have to call something like this $r->set_handlers(PerlInitHandler => undef); from some other handler or somesuch. HTH --Geoff -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
