>True. As for praise, XML::Parser does the job for me. In this specific
>case, I'll be looking for something like failure in the
>response to an XML request I send. I'd like to pull out just the section
>that failed and be able to create another request from that XML chunk.
>It's a little down the
ECTED]]Sent: Monday, October 09, 2000 4:02
PMTo: Herrington, Jack; '[EMAIL PROTECTED]'Subject: RE:
:Parse segmentation fault
Hmmm
well I *have* to have Xml parsing. Not sure if what you are suggesting totally
turns it off or just does something else?
-Original M
: Monday, October 09, 2000 3:43
PMTo: Herrington, Jack; '[EMAIL PROTECTED]'Subject: RE:
:Parse segmentation fault
Yes. We found a problem in Expat.pm line 451 (in sub
parse). The following chunk of code (latest version from cpan)
sub parse { my $self =
shift; my $a
This code works as a perl script executed off the command line:
use XML::Parser;
my $parser = new XML::Parser();
$parser->parse( "" );
This code fails with a segmentation fault when called from mod_perl:
package CBL::mod_perl::test1;
use strict;
Compile-time? You mean, when I compile Perl 5.6 I can permanently disable
taint checking?
-Original Message-
From: Vivek Khera [mailto:[EMAIL PROTECTED]]
Sent: Monday, October 02, 2000 11:04 AM
To: Herrington, Jack
Cc: '[EMAIL PROTECTED]'
Subject: RE: Taint
>>>&g
>> 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
A couple of questions about taint checking.
1) What is the default taint check setting?
2) Does compiling mod_perl with EVERYTHING=1 make a difference to the taint
setting?
3) Does 'PerlTaintCheck Off' actually work?
4) How do I check the taint setting at run-time from a perl handler?
Thanks!
I'm using Mason in process with mod_perl. I have also tried using mod_perl
handlers direct with Apache::Request with no success.
-Original Message-
From: Doug MacEachern [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, September 26, 2000 10:23 AM
To: Herrington, Jack
Cc: [EMAIL PROT
>well, if you don't have that, then you likely don't have Apache::Request or
>Apache::Cookie - they aren't part of the mod_perl distribution :)
>you need libapreq, which can be found under the Apache tree on CPAN
libapreq appears to come with Bundle::Apache, but I also downloaded it
seperately an
I have the same problem as one of the previous reporters with
Apache::Request->new(). The problem occurs whether I call it after a 'use'
or after a 'PerlModule' load. Perl returns the no 'new' method could be
found for Apache::Request.
My setup is:
Apache 1.3.12
mod_perl 1.24
Perl 6.5
Redhat 6
10 matches
Mail list logo