>
>
> SetHandler perl-script
> PerlResponseHandler Work::Access::Login
> PerlOptions +ParseHeaders
> ErrorDocument 403 /login
>
> Additionally, a 500 Internal Server Error error was encountered while
> trying to use an ErrorDocument to handle
Since converting over to mp2 about a year ago, we seem to be having
intermittent problems with ErrorDocument.
This is the current configuration in the apache.conf file.
SetHandler perl-script
PerlResponseHandler Work::Blah
PerlOptions +ParseHeaders
ErrorDocumen
Ack -- ignore that, problem solved. I wasn't loading the apreq2 module in my
apache2.conf file.
On 6/26/07, Eric Adum <[EMAIL PROTECTED]> wrote:
Hi,
I'm trying to write a handler for mod_perl 2.0.
I have a sub of the form
sub handler {
my $r = shift;
my $req = Apache2::Request->new($r)
Hi,
I'm trying to write a handler for mod_perl 2.0.
I have a sub of the form
sub handler {
my $r = shift;
my $req = Apache2::Request->new($r);
print "Something.";
return Apache2::Const::OK();
}
When I go to the URL associated with the handler, I get a blank page,
nothing in the error l
I've been looking at how you would add object and embed tags, and it
isn't trivial. They're not in there by default because of the nasty
things that they can do. But I could add them in, along with flags to
specify that you want to allow them, much like AllowHref
I'll get back to you.
Again, I'
On Jun 26, 2007, at 11:09 AM, Clinton Gormley wrote:
allowScriptAccess="never"
allownetworking="internal"
I don't know what those are :)
tags are removed by default, and you would still need to
subclass HTML::StripScripts in order to allow those elements.
The Rules (for sa
> Actually, something I would feel would be very useful is if it could
> return an XML::LibXML::DocumentFragment object.
>
> I tend to use XML::LibXML to parse user input and insert in the
> document, which is then going through some XSLT, and since you've
> allready parsed stuff, it seems li
On Tue, 2007-06-26 at 11:02 -0400, Jonathan Vanasco wrote:
> On Jun 26, 2007, at 10:22 AM, Clinton Gormley wrote:
>
> > HTML::StripScripts
>
> thanks! I'm already a happy user.
> excited to check out the changelog.
>
> does the new version automagically do the anti-xss flash embed
> extension
On Tuesday 26 June 2007 16:22, Clinton Gormley wrote:
> - used to strip XSS scripting from user submitted HTML
Ooooh, cool! I haven't found any modules that does that well enough.
> - outputs valid HTML (cleans up nesting, context of tags etc)
>
> - handles the exploits listed at http://ha.cke
Hi all
I've recently released two modules to CPAN which are of relevance to
mod_perl developers, one as the author and one as the maintainer.
I realise this is a blatant plug, but these modules have been useful to
me in my web-app work, and so there is a good chance that they will be
useful to ot
On 26 Jun 2007, at 13:44, Geoffrey Young wrote:
Mark Blackman wrote:
The problem: PerlChildInitHandler handler appears to runs in the
parent
instead of the child.
After duplicating the code in
http://perl.apache.org/docs/2.0/user/handlers/server.html
for MyApache2::Startuplog.pm in the fo
Mark Blackman wrote:
> The problem: PerlChildInitHandler handler appears to runs in the parent
> instead of the child.
>
> After duplicating the code in
> http://perl.apache.org/docs/2.0/user/handlers/server.html
> for MyApache2::Startuplog.pm in the following environment.
>
> Apache/2.2.4 (Uni
The problem: PerlChildInitHandler handler appears to runs in the
parent instead of the child.
After duplicating the code in http://perl.apache.org/docs/2.0/user/
handlers/server.html
for MyApache2::Startuplog.pm in the following environment.
Apache/2.2.4 (Unix) mod_ssl/2.2.4 OpenSSL/0.9.7i m
13 matches
Mail list logo
