rcial use.
Another one is Greymatter (http://www.noahgrey.com/greysoft/) which is
totally free.
Thirdly (but not lastly in any way), there's Scoop
(http://scoop.kuro5hin.org/) which I had never heard of before, but
seems to explicitly use mod_perl in some way.
Martijn.
chive-location, should both
handlers return OK (logical AND) or is it enough if one does (logical
OR)?
I always assumed it was logical AND and that makes sense to me in at
least ten different ways, but I'd rather be 100% sure, before I
accidentally open up half of our site...
Thanks.
Martijn.
great deal understanding mod_perl in
general. And yes, I too wonder why I had never done it in the past. :)
Martijn
block access to mydomain.com/test in the setup copied below
and write a line in error_log.
I am afraid I am making a stupid mistake somewhere, but I can't find
where. Any help would be greatly appreciated.
Thanks.
Martijn.
---
In httpd.conf:
PerlModule Testhandler
# PerlAccessHandler T
t under its own name-
but if I understand things correctly, it is standard part of Apache.
Am I missing something?
Thanks.
Martijn.
eplaced by something better and shouldn't be used anymore. My guess
would be the latter.
Which made me wonder: is there a nice way to use mod_perl to keep evil
visitors away? Preferably using heuristics rather than a black list of
bad IP addresses.
Martijn
This, of course, is the solution. Thanks, both!
In case you wonder why I hadn't just copied a working handler and
started by changing that, I wonder too. Stubborn is my middle name, I
am afraid.
Martijn
On 3/1/07, Martin Moss <[EMAIL PROTECTED]> wrote:
As I understand it...
if y
;autologin
to
PerlAuthenHandler MyRoot::Testing::autologin
It's doing my head in, as in the line above this one, a -> is used
without any problems. It's all not very important, but I'd like to
write code of which I understand why it works, rather than code that
just happens to work.
Martijn.
, but it just isn't very tidy. And I just like
to understand things.
Thanks.
Martijn
