Thanks. :) Although I am not sure if this will help the person in question... I think that persistent Perl seems to run into some odd/interesting issues where taint mode is triggered in some odd ways. I've never encountered it myself but I've heard from others that there is some weird stuff going on. Of course, if you want to untaint a variable just do... $tainted =~ /(.*)/; $tainted = $1; Of course, the FAQ says dont do this because you may not understand why the taint mode has triggered something and that cause should be rectified by a more precise expression. In addition, if the taintmode errors are being triggered in Mason, then I find it hard to believe that Mason does not already take care of this for its users. At 01:09 PM 10/3/00 -0400, ricarDo oliveiRa wrote: >I hope this can help you: > >http://www.gunther.web66.com/FAQS/taintmode.html > >------Original Message------ >From: "Herrington, Jack" <[EMAIL PROTECTED]> >To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> >Sent: October 2, 2000 5:23:51 PM GMT >Subject: RE: Taint > > > >> 4) How do I check the taint setting at run-time from a perl handler? > >I'm not sure that you can. PerlTaintCheck On or Off applies to all perl > >scripts/handlers... > >see http://perl.apache.org/guide/porting.html#Taint_Mode > >The problem that I am having is that I am getting taint errors in mason >without taint being turned on. So it makes me think that taint is actually >on. > >Is there a way to enable and disable taint checking at run-time? > >------------------ >./ricarDo oliveiRa >______________________________________________ >FREE Personalized Email at Mail.com >Sign up at http://www.mail.com/?sr=signup
