On Wed, 2002-02-13 at 13:44, David Wheeler wrote:
> On Fri, 2002-02-08 at 20:25, Salvador Ortiz Garcia wrote:
> > Yes, It's a bug in Sections. Confirmed in 1.26.
>
>
>
> > I'm digging into it.
>
> Thanks. I'm glad to know that I'm not imagining things. We've just found
> a place in Bricolage
Yes.
R. Beazley
-Original Message-
From: Rodney Broom [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 13, 2002 7:55 PM
To: OCNS Consulting; [EMAIL PROTECTED]
Subject: Re: mod_perl compile problem
From: OCNS Consulting <[EMAIL PROTECTED]>
> I'm attempting to make "httpd" apache-1.
I checked it out and it's a good mod. I've already got the ability to log
the data however. The issue that I'm having is that I can't seem to only get
1 log per hit. I can't seem to get around the fact that wherever I put my
mod (PerlFixupHandler,PerlHandler,PerlLogHandler) or whatever statement I
Yes.
R. Beazley
-Original Message-
From: Rodney Broom [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 13, 2002 7:55 PM
To: OCNS Consulting; [EMAIL PROTECTED]
Subject: Re: mod_perl compile problem
From: OCNS Consulting <[EMAIL PROTECTED]>
> I'm attempting to make "httpd" apache-1.
From: OCNS Consulting <[EMAIL PROTECTED]>
> I'm attempting to make "httpd" apache-1.3.23 with mod_perl-1.26 and
> ActiveState Perl 5.6.1 Build 631.
Am I hearing you right, you're using an ActiveState Perl on Linux?
---
Rodney Broom
Programmer: Desert.Net
Hi:
I'm attempting to make "httpd" apache-1.3.23 with mod_perl-1.26 and
ActiveState Perl 5.6.1 Build 631. This is a simple build with no other
modules or EAPI references. Unfortunately, I'm encountering the following
error when the compile of the "http_core.c" routine is attempted:
gcc -c -I..
All good points. This code is only to test mod_perl Perl*Handler mechanisms
to ensure that I can get the proper log. Once I figure out the necessary
routines to do this then I'll integrate it with the rest of my mod, which
logs request and session info to a database.
-- Ryan
- Original Messa
On Wed, 13 Feb 2002, Ryan Parr wrote:
> The code follows:
> sub handler {
> my $r = shift;
> return DECLINED unless($r->is_main());
> # Same behavior when:
> # return DECLINED unless($r->is_initial_req());
>
> open TRACK, ">>/usr/local/www/usertracker.txt"
File::Spec is in included with the standard perl mods I believe
so dependencies shouldn't be a problem.
> I see. You're right, this is actually much nicer!
>
> Sorry for the misinformation. On debian it return : also. I made a
> mistake checking it.
>
> But with the suggested code by Per it wo
I see. You're right, this is actually much nicer!
Sorry for the misinformation. On debian it return : also. I made a
mistake checking it.
But with the suggested code by Per it works just fine:
sub load {
my $module=@_[0];
$module = File::Spec->catfile(split /::/, $module);
$modu
Cool . . .
Thanks for the tip : )
> > > The easiest thing would be to use Config, and do:
> > >
> > > $module =~ s[::][$Config{'path_sep'}]g;
> > >
> > > Right?
> >
> >Maybe not : ) When checking on 2 linux systems I got a path seperator of
> >':'. Can you let me know if you get similar resu
Nothing special to the way these sites work. You can check out
http://www.rileyjames.com and http://www.ryanparr.com (the programming on
the latter will leave you in awe :) I want to host my sites and have a
decent usage statistics location, but I just can't seem to get the logging
part down. I've
Sorry, this code does not work... Should test it better before sending
it to to mailing list...
Marcel
Am Donnerstag den, 14. Februar 2002, um 00:05, schrieb Marcel Weber:
> So here comes the most actual code:
>
> Submitting it to CPAN would be fine!
>
> ---
Interesting, one system is RedHat 7.2 and Suse 7.3 (custom built perl) that
returns
a ':' for $Config{'path_sep'}
> It returns a arrayref, as far as I experienced. Well I'm really new to
> mod_perl
> and my eagle book waits still in the library to be bought... But why is
> this
> version not ni
At 16:51 13.02.2002 -0600, Stathy G. Touloumis wrote:
> > The easiest thing would be to use Config, and do:
> >
> > $module =~ s[::][$Config{'path_sep'}]g;
> >
> > Right?
>
>Maybe not : ) When checking on 2 linux systems I got a path seperator of
>':'. Can you let me know if you get similar re
On my woody system it's fine.
Marcel
Am Mittwoch den, 13. Februar 2002, um 23:51, schrieb Stathy G. Touloumis:
>> The easiest thing would be to use Config, and do:
>>
>> $module =~ s[::][$Config{'path_sep'}]g;
>>
>> Right?
>
> Maybe not : ) When checking on 2 linux systems I got a path seper
So here comes the most actual code:
Submitting it to CPAN would be fine!
package Apache::AuthMulti;
# Stathy G. Touloumis
# Marcel M. Weber
# Darren Chamberlain
#
# Version 0.01-2 / 13.02.2002 / Marcel M. Weber
use strict;
use Apache::C
> The easiest thing would be to use Config, and do:
>
> $module =~ s[::][$Config{'path_sep'}]g;
>
> Right?
Maybe not : ) When checking on 2 linux systems I got a path seperator of
':'. Can you let me know if you get similar results?
Thanks,
On Wed, 13 Feb 2002, Ryan Parr wrote:
> Unfortunately we do have areas on the site where a link would point directly
> to a graphic file, which I'd like to log. Otherwise that would work quite
> well.
>
> I had always thought that these extra requests would be subrequests. If not,
> though, what
Unfortunately we do have areas on the site where a link would point directly
to a graphic file, which I'd like to log. Otherwise that would work quite
well.
I had always thought that these extra requests would be subrequests. If not,
though, what would be the definition of a sub-request?
-- Ryan
> > I would suggest changing the PerlSetVar variables
> > to actual apache configuration directives which would change this :
> >
> > my @auth_modules=$r->dir_config->get("AuthModules");
> >
> > I don't have an immediate patch for this but have done it before.
> > If you would like me to work on
Quoting Stathy G. Touloumis <[EMAIL PROTECTED]> [13 Feb-02 15:26]:
> Some more fixes ; )
Yay! Bug reports already...
> I would suggest changing the PerlSetVar variables
> to actual apache configuration directives which would change this :
>
> my @auth_modules=$r->dir_config->get("AuthModules");
Some more fixes ; )
I would suggest changing the PerlSetVar variables
to actual apache configuration directives which would change this :
my @auth_modules=$r->dir_config->get("AuthModules");
I don't have an immediate patch for this but have done it before.
If you would like me to work on this c
>
>
> I think you might need to iterate through $r->err_headers_out and
> remove WWW-Authenticate and Proxy-Authenticate after each
> authentication module runs.
>
> say you have an AuthSMB and AythSybase chain. AuthSMB calls
> note_basic_auth_failure and sets the WWW-Authenticate header,
> A
> "Marty" == Marty J Rogers <[EMAIL PROTECTED]> writes:
Marty> I had tried that, with the same result. (does Apache::DBI
Marty> overload the DBI methods?) Full error is as follows. Again,
Marty> any help is _highly_ appreciated.
You must specify the full package name to the conne
Marcel Weber wrote:
>
> Fixed some errors. Here comes the working version:
>
I think you might need to iterate through $r->err_headers_out and
remove WWW-Authenticate and Proxy-Authenticate after each
authentication module runs.
say you have an AuthSMB and AythSybase chain. AuthSMB calls
no
On Wed, 13 Feb 2002, Ryan Parr wrote:
> I'm trying to setup some custom logging including the whole
> User/Session tracking thing. The problem that I'm encountering is
> how to log for the page that was requested and ignore all the
> additional files that may be included in the page. I.e. graphic
Do you need to expire the cookie when you leave the page? How about the
following.
When they login, you send down a cookie. when they go to that page, you
check the cookie they sent, but send out a new value for that cookie,
invalidating it. So when they leave that page they send back your
inval
Quoting Marcel Weber <[EMAIL PROTECTED]> [13 Feb-02 14:53]:
> Why not submitting this somewhere? I think this could be
> usefull for quite a lot of people. I think this is cool, as you
> do not have to worry wether the module returns DECLINED or
> AUTH_REQUIRED.
I can package this up and put it o
I have sometimes proposed or recommended schemes of storing session
information in an HTTP cookie, encoded and protected by cryptographic
digest. I know some people on this list have implemented similar
schemes, but I have never actually had occasion to do so. Now I am
doing that, and I realize
Fixed some errors. Here comes the working version:
-
package Apache::AuthMulti;
# Stathy G. Touloumis
# Marcel M. Weber
# Darren Chamberlain
#
# Version 0.1.0 / 2002.02.13 / Marcel M. Weber
use strict;
use Apache::Constants qw(:common);
sub handler {
my $r = shift;
On Fri, 2002-02-08 at 20:25, Salvador Ortiz Garcia wrote:
> Yes, It's a bug in Sections. Confirmed in 1.26.
> I'm digging into it.
Thanks. I'm glad to know that I'm not imagining things. We've just found
a place in Bricolage where the Location directive *does* work as
expected. So you're righ
--
mod_perl digest
February 3, 2002 - February 9, 2002
--
Recent happenings in the mod_perl world...
Features
> the only problem is that,
> for the PerlAuthenHandler and PerlAuthzHandler the first handler to
> return an Apache error code (anything other than OK, DECLINED, or
> DONE) terminates the chain. which is generally fine, except when you
> want to return AUTH_REQUIRED and note_basic_auth_failure()
On page leave? Well I think you can of course use javascript on all the
links on the page, but I don't believe you can do much about the user
typing in a new url in the browser. . .
but that's just IMHO.
--Jon
Ryan Parr wrote:
>
> I think I'm missing something...
>
> If you set a session coo
Aaron Ross wrote:
>
> shouldn't stacked handlers be the right solution here? are stacked auth
> handlers not allowed or something?
>
yes, you can stack multiple auth handlers. the only problem is that,
for the PerlAuthenHandler and PerlAuthzHandler the first handler to
return an Apache error
He wants to check a 'handler' return value.
> shouldn't stacked handlers be the right solution here? are stacked auth
> handlers not allowed or something?
>
> aaron
>
> On Wed, 2002-02-13 at 09:02, darren chamberlain wrote:
> > Quoting Marcel Weber <[EMAIL PROTECTED]> [12 Feb-02 16:15]:
> > >
Quoting Aaron Ross <[EMAIL PROTECTED]> [13 Feb-02 09:21]:
> shouldn't stacked handlers be the right solution here? are
> stacked auth handlers not allowed or something?
Assuming your mod_perl has been built with them, then, yes, that's
probably a better solution. But I had a fun 15 minutes writ
shouldn't stacked handlers be the right solution here? are stacked auth
handlers not allowed or something?
aaron
On Wed, 2002-02-13 at 09:02, darren chamberlain wrote:
> Quoting Marcel Weber <[EMAIL PROTECTED]> [12 Feb-02 16:15]:
> > I don't get the point why it did not work the other way round
Quoting Marcel Weber <[EMAIL PROTECTED]> [12 Feb-02 16:15]:
> I don't get the point why it did not work the other way round,
> but now everything is just fine now :
Make it a little more generic:
package Apache::MultiAuthen;
use strict;
use Apache::Constants qw(:common);
sub handler {
my $
On Tue 12-Feb-2002 at 04:02:47PM -0500, Perrin Harkins wrote:
> > A list of things I've noticed:
> >
> > * If you have two *different* modules which have the same name, then
> > either one, or the other is loaded in memory, never both. This is
> > dead annoying. I think Perl standard modules + CPA
you can use sessions... there are some modules for this. Forexample,
Apache::ASP has the $Session object... or you can use javascript to delete
the cookie (maybe)
-Original Message-
From: Ryan Parr [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 13, 2002 11:00 AM
To: Jon Robison; Ron
I'm trying to setup some custom logging including
the whole User/Session tracking thing. The problem that I'm encountering is how
to log for the page that was requested and ignore all the additional files that
may be included in the page. I.e. graphics. Without trying to maintain session
uni
> >Syntax error on line 346 of /usr/local/apache/conf/httpd.conf:
> >Can't load
> >'/usr/local/lib/perl5/site_perl/5.6.1/sun4-solaris/auto/Authen/Smb/Smb.so' for
> >module Authen::Smb: ld.so.1: /usr/local/apache/bin/httpd: fatal: relocation
> >error: file
> >/usr/local/lib/perl5/site_perl/5.6.1/su
I think I'm missing something...
If you set a session cookie (i.e. one with no expiry time) then the cookie
will be deleted immediately upon browser close, forcing the user to login
again if they've closed their browser instance.
If you don't use cookies and allow basic auth then the exact same
45 matches
Mail list logo