All,
I am working on Recipe 3.4. I have the following saved as cgi-perl/try.pl:
#! /usr/bin/perl -w
# file: try.pl
use strict;
use Apache::Const qw(:common);
my $r=shift;
# Grab all of the headers at once
my %headers_in=$r->headers_in;
# or get a specific header and do something with it
my $g
Perrin Harkins wrote:
On Fri, 2004-07-02 at 17:18, David Arnold wrote:
I did a little searching and saw very little on Apache-Test.
Really? It's all over the mod_perl site. This would be a good place to
start:
http://perl.apache.org/docs/general/testing/testing.html
Is it a current CVS project?
On Fri, 2004-07-02 at 17:18, David Arnold wrote:
> I did a little searching and saw very little on Apache-Test.
Really? It's all over the mod_perl site. This would be a good place to
start:
http://perl.apache.org/docs/general/testing/testing.html
> Is it a current CVS project?
It's on CPAN. G
Stas,
>Again, do not test your modperl code w/o running modperl, which you
accomplish
>with help of Apache-Test.
I did a little searching and saw very little on Apache-Test. Is it a
current CVS project? If so, I've never participated or downloaded such a
thing.
However, you seem to think it wou
David Arnold wrote:
Stas,
package Apache::AuthAnon;
# file: Apache/AuthAnon.pm
use strict;
use Apache::Constants qw(:common);
my $email_pat='[EMAIL PROTECTED]';
my $anon_id="anonymous";
sub handler {
my $r=shift;
my($res,$sent_pwd)=$r->get_basic_auth_pw;
return $res if $res!=OK;
my $us
Stas,
>> package Apache::AuthAnon;
>> # file: Apache/AuthAnon.pm
>>
>> use strict;
>> use Apache::Constants qw(:common);
>>
>> my $email_pat='[EMAIL PROTECTED]';
>> my $anon_id="anonymous";
>>
>> sub handler {
>> my $r=shift;
>>
>> my($res,$sent_pwd)=$r->get_basic_auth_pw;
>> retur
David Arnold wrote:
All,
I get so confused keeping track of everything. I've got some modules that I
swear checked for syntax a few days ago. Here's one that starts:
package Apache::AuthAnon;
# file: Apache/AuthAnon.pm
use strict;
use Apache::Constants qw(:common);
my $email_pat='[EMAIL PROTECTED]'
Stas Bekman wrote:
> From Changes:
=item 1.21_03 - March 15, 2000
new variable $Apache::Server::StrictPerlSections, if true, will croak
section generates invalid Apache configuration syntax
Does it do the trick? I'm not sure why it's not documented.
Where should I put this?
I've tried adding it
All,
I get so confused keeping track of everything. I've got some modules that I
swear checked for syntax a few days ago. Here's one that starts:
package Apache::AuthAnon;
# file: Apache/AuthAnon.pm
use strict;
use Apache::Constants qw(:common);
my $email_pat='[EMAIL PROTECTED]';
my $anon_id="a
Perrin Harkins wrote:
On Fri, 2004-07-02 at 14:07, Bevelock, Mike wrote:
Actually, all our required libs declare a package...I guess that's why it's
working for us.
I don't see any harm in adding it, if it helps some people. Could you
add a little bit to the docs to explain your addition, and the
On Fri, 2004-07-02 at 14:07, Bevelock, Mike wrote:
> Actually, all our required libs declare a package...I guess that's why it's
> working for us.
I don't see any harm in adding it, if it helps some people. Could you
add a little bit to the docs to explain your addition, and the caveat
that it on
benoit wrote:
Stas Bekman wrote:
> From Changes:
=item 1.21_03 - March 15, 2000
new variable $Apache::Server::StrictPerlSections, if true, will croak
section generates invalid Apache configuration syntax
Does it do the trick? I'm not sure why it's not documented.
Where should I put this?
startu
> -Original Message-
> From: Perrin Harkins [mailto:[EMAIL PROTECTED]
> Sent: Friday, July 02, 2004 12:05 PM
> To: Bevelock, Mike
> Cc: '[EMAIL PROTECTED]'
> Subject: Re: Apache::Reload: explicitly registering required
> library files [p atch included]
>
>
> Bevelock, Mike wrote:
> > Fo
benoit wrote:
Ok, now I'm ashamed.
After some more RTFM, I found that there was a missing-closing-parens
festival going on in my configuration file...
So, for the record and/or those who will find this message some
debugging day :
I followed the suggestion of Pratical Mod_perl, p.132 : I've add
Bevelock, Mike wrote:
For example, if a sub in 'lib/common_subs.pl' changed, it would be nice if
all code
that did this:
require 'lib/common_subs.pl';
got the fresh code in lib/common_subs.pl.
It won't with this patch, unless common_subs.pl declares a package. If
common_subs.pl is just a bunch of
A nice enhancement to Apache::Reload would be the ability to explicitly
"register" and reload required library files.
For example, if a sub in 'lib/common_subs.pl' changed, it would be nice if
all code
that did this:
require 'lib/common_subs.pl';
got the fresh code in lib/common_subs.pl.
The Ap
Ok, now I'm ashamed.
After some more RTFM, I found that there was a missing-closing-parens
festival going on in my configuration file...
So, for the record and/or those who will find this message some
debugging day :
I followed the suggestion of Pratical Mod_perl, p.132 : I've added a a
#!/usr
Hello.
I'm trying to build an Apache configuration that makes it possible for
all the developpers in my group to work with their own Apache process.
For doing so, I'm using sections that build the server
configuration; changing the User/Group, dynamically ajusting the
DocumentRoot and Port, et
18 matches
Mail list logo
