Many cobalt boxes come running mod_perl by default. perhaps if people have
been deploying a lot of these things lately it could have made an impact.
HEAD / HTTP/1.0
HTTP/1.1 302 Found
Date: Mon, 04 Feb 2002 20:13:54 GMT
Server: Apache/1.3.12 Cobalt (Unix) mod_jk mod_ssl/2.6.4 OpenSSL/0.9.5a
P
Last week there was a post to bugtraq about ways to exploit badly written
scripts using cdonts.newmail, that exploited the fact that there was a SMTP
conversation going on behind the scenes. This type of exploit can probably
be used on a ton of other form mail type things, that use SMTP in the b
i may be wrong about this, but since the file is actually part of the POST,
apache cannot start returning something for that request before the request
has been finished. You can get around this, kind of, using a JS popup
onsubmit, that opens a window that somehow lets you check the status of th
> > The perldoc Apache::Registry says
> > "Apache::Registry - Run unaltered CGI scrips under mod_perl"
>
> Were your CGI scripts designed to handle HEAD requests? You
> don't have
> to alter them to run under mod_perl, do you?
You didn't have to design them to because apache handles it for yo
huh? doesn't that mean that the person who is running the tool doesn't use
HTML or other code, not the person that wrote the tool?
I'd have to agree that it's not really applicable though since it talks
about it running offline, and about selecting widgets for the site and stuff
along those line
I was looking through the mod_perl archives and saw a post from doug about a
credit card processing system called 'creditor' i looked on the covalent
web site, but i couldn't find any info. Did this thing ever see the light
of day?
If not, what are some alternatives to it? i was forwarded t
I've run into this before as well, and what i ended up doing to get around
it was keeping the original $r around long enough to call filter_register.
my $r = shift;
my $req = Apache::Request->new($r);
$r = $r->filter_register();
adam
> -Original Message-
> From: Trevor Phillips [
Maybe it's just me, but it seems that the responses richard has gotten
haven't really touched on the core of the problem. That mod_perl isn't
exactly friendly to sysadmin's who want to run apache on a (i'm guessing),
student accessed server, with user dir's and all that other stuff. I'm
pretty s
> why do you want to process a directory listing? you want to
> process the files within the directory via SSI, right?
I ran into this too, so i'll explain what i was trying to do. I have a
handler that works like this
SetHandler perl-script
PerlHandler Site::Articles
I'm trying to install apache filter and i'm getting errors. anyhelp would
be appreciated.
i built mod_perl with this:
perl Makefile.PL DO_HTTPD=1 USE_APACI=1 APACHE_PREFIX=/usr/local/apache
PERL_STACKED_HANDLERS=1
when i get to make test i get this:
Running make test
PERL_DL_NONLAZY=1 /usr/bi
10 matches
Mail list logo