lly I find Template Toolkit easier to use than Mason when I want
to do the kind of things that I would once upon a time have done with
PHP...
Cheers,
Nick
--
Nick Phillips / +64 3 479 4195 / [EMAIL PROTECTED]
# these statements are my own, not those of the University of Otago
y universe, it's
*that*
one that should be called something else. It seems from what I remember
to be
more similar to autotools' ${prefix}.
Cheers,
Nick
--
Nick Phillips / +64 3 479 4195 / [EMAIL PROTECTED]
# these statements are my own, not those of the University of Otago
On 30/10/2004, at 7:19 AM, Stas Bekman wrote:
CN wrote:
Hi!
Because "perl Makefile.PL" did not find LWP::UserAgent and
HTML::HeadParser in my Debian box, I did "apt-get install
libapache-mod-perl". Then I did "dpkg -P libapache-mod-perl" to remove
that package. Since then "perl Makefile.PL" seems t
weren't previously packaged, for example. And gcc 3.3...
Cheers,
Nick
--
Nick Phillips / +64 3 479 4195 / [EMAIL PROTECTED]
# these statements are my own, not those of the University of Otago
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modpe
using SSL to test
this.
I seem to recall a known IE bug with the way it drops connections when
using
SSL. Maybe google for "ssl-unclean-shutdown" together with "MSIE"? I
think it
also suffers when keepalive is used, in that sometimes it will send
incorrect
content-length hea
gout {
my ($self) = @_;
my $authtype = $self->{apr}->auth_type;
if (defined $authtype) {
$authtype->logout($self->{apr});
}
else {
# ??
}
}
...that works fine.
Cheers,
Nick
--
Nick Phillips / +64 3 479 4195 / [EMAIL PROTECTED]
# these stateme
imilar.
This is because it is read in a BEGIN block, and there is no current
request and hence no
appropriate virtual host at that stage.
It's in the docs, IIRC.
Cheers,
Nick
--
Nick Phillips / +64 3 479 4195 / [EMAIL PROTECTED]
# these statements are my own, not those of the Univ
owing aliases.
Could someone suggest a configuration that would permit LOGIN to
invoke Apache::AuthCookie->login correctly but still protect the
entire docroot?
Are you currently using or tags to configure
protection for the main body
of your content?
Cheers,
Nick
--
Nick Phillips / +
Begin forwarded message:
From: Stas Bekman <[EMAIL PROTECTED]>
Date: 15 December 2003 9:32:14 AM
To: Nick Phillips <[EMAIL PROTECTED]>
Subject: Re: Testing
Nick, can you please repost your reply back to the thread on the list?
THanks.
Sure...
Nick Phillips wrote:
On 12/12/2003, at 5
(such interaction is
usually Bad,
in my experience).
Any top tips?
Cheers,
Nick
--
Nick Phillips / +64 3 479 4195 / [EMAIL PROTECTED]
# these statements are my own, not those of the University of Otago
--
Reporting bugs: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
On 12/12/2003, at 8:34 AM, Garrett Goebel wrote:
Nick Phillips wrote:
>
> Just wondering whether anyone here has any cunning ways of
> unit testing code that uses the various Apache:: modules;
> the only vaguely useful thing I've managed to find so far
> is Apache::FakeReq
urely *someone* has done it before?...
Cheers,
Nick
--
Nick Phillips / +64 3 479 4195 / [EMAIL PROTECTED]
# these statements are my own, not those of the University of Otago
--
Reporting bugs: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
12 matches
Mail list logo
