On Thu, Feb 21, 2019 at 02:35:22AM +, Jie Gao (j@sydney.edu.au) wrote:
> * Jobst Schmalenbach wrote:
>
> Not sure how you went with this issue, but you might want to try this instead:
>
>
> Require user USER1 USER2
>
> Require ip 127.0.0.1
> Require host localho
* Jobst Schmalenbach wrote:
> Date: Wed, 20 Feb 2019 12:33:22 +1100
> From: Jobst Schmalenbach
> To: modperl@perl.apache.org
> Subject: Apache upgrade 2.2 -> 2.4 and "PerlAuthenHandler
> Authen::Simple::IMAP"
> User-Agent: Mutt/1.9.1 (2017-09-22)
>
> I po
On Wed, Feb 20, 2019 at 02:11:14PM +, John Dunlap (j...@lariat.co) wrote:
> Have you tried adding "Require all granted" inside the directory tag?
That would defeat the purpose of my problem.
If I do "Require all granted" the directory would not be protected,
he password query would not come up
do with the .htaccess file, I just got a login box.
> I saw this:
>
> https://www.gsp.com/cgi-bin/man.cgi?topic=Authen::Simple::Passwd
>
> which has a different setup than the .htaccess I specified
>
> PerlModule Authen::Simple::Apache
> PerlModule Authen::Si
e
PerlModule Authen::Simple::Passwd
PerlSetVar AuthenSimplePasswd_path "/etc/passwd"
PerlAuthenHandler Authen::Simple::Passwd
AuthType Basic
AuthName "Protected Area"
Require valid-user
They are ACTUALLY specifying the MODULES which I did not do.
Need to
On Tue, Feb 19, 2019 at 06:14:53PM -0800, Paul B. Henson (hen...@acm.org) wrote:
> On 2/19/2019 6:02 PM, Jie Gao wrote:
> > Found this on CPAN:
> >
> > Module < Authen::Simple::IMAP (DMARTIN/Authen-Simple-IMAP-0.1.2.tar.gz)
>
> Hmm, perhaps I should have searched CPAN directly rather than rely
On Wed, Feb 20, 2019 at 02:02:54AM +, Jie Gao (j@sydney.edu.au) wrote:
> * Paul B. Henson wrote:
>
> >
> > https://metacpan.org/pod/Authen::Simple
> >
> > which does not appear to include an IMAP component.
>
> Found this on CPAN:
>
> Module < Authen::Simple::IMAP (DMARTIN/Authen-
On 2/19/2019 6:02 PM, Jie Gao wrote:
Found this on CPAN:
Module < Authen::Simple::IMAP (DMARTIN/Authen-Simple-IMAP-0.1.2.tar.gz)
Hmm, perhaps I should have searched CPAN directly rather than relying on
Google :). Thanks for the pointer…
The last update for this module was in 2009; Apa
* Paul B. Henson wrote:
> Date: Tue, 19 Feb 2019 17:50:15 -0800
> From: "Paul B. Henson"
> To: modperl@perl.apache.org
> Subject: Re: Apache upgrade 2.2 -> 2.4 and "PerlAuthenHandler
> Authen::Simple::IMAP"
> User-Agent: Mozilla/5.0 (Windo
On 2/19/2019 5:33 PM, Jobst Schmalenbach wrote:
While I have fixed most of the issues realted to the upgrade of
Apache one I cannot solve is the "PerlAuthenHandler
Authen::Simple::IMAP" in .htaccess files.
The authentication/authorization API changed between 2.2/2.4, if this
modu
the version number.
While I have fixed most of the issues realted to the upgrade of Apache one I
cannot solve is the "PerlAuthenHandler Authen::Simple::IMAP" in .htaccess files.
I use this rather frequently on many machines as it is real easy for me to look
after this.
Using apach
Ahh, very interesting.
I actually did want to use a full url with scheme and host.
What we wanted was a response of type HTTP_UNAUTHORIZED with a Location header
as well as the other headers I added.
But, perhaps that's not a reasonable thing to want, and we can provide a URI to
a page on the
On Saturday, May 28, 2011 21:10:14 Matisse Enzer wrote:
> $r->custom_response( HTTP_UNAUTHORIZED, $uri );
> return HTTP_UNAUTHORIZED
Make sure $uri does not contain the hostport part. It must start with a
slash. The next lines are from modules/http/http_request.c:
/*
* Two types
Using Apache/2.2.17 mod_perl/2.0.5.
We have a PerlAuthenHandler that (on failure to authenticate) sets two headers
('Set-Cookie' and 'WWW-Authenticate' and returns HTTP_UNAUTHORIZED. We also use
$r->custom_response to set a URL as the response body.
What I expect Apach
e.org
Subject: Re: POST method and PerlAuthenHandler
Use apreq.
From: James B. Muir
To: "modperl@perl.apache.org"
Sent: Thu, January 27, 2011 11:08:24 AM
Subject: POST method and PerlAuthenHandler
Hello,
I am writing a perl authentication module for Apache2 that must inspect some
req
Use apreq.
>
>From: James B. Muir
>To: "modperl@perl.apache.org"
>Sent: Thu, January 27, 2011 11:08:24 AM
>Subject: POST method and PerlAuthenHandler
>
>
>Hello,
>
>I am writing a perl authentication module for Apache2 that must inspect some
&g
Hello,
I am writing a perl authentication module for Apache2 that must inspect some
request parameters before authorizing the requestor and forwarding the request
to a tomcat server via mod_jk.
With the GET request method this is easy, I can inspect the parameters using
$r->args and forward th
>
>> Today I tried to limit access to phpMyAdmin using my own Authen.pm
>> module. It works well but not always. Looks like phpMyAdmin has
>> problems with HTTP post method if I enable my PerlAuthenHandler
>> Authen.pm. Otherwise phpMyAdmin and Authen.pm work well.
>>
&
hpMyAdmin using my own Authen.pm
module. It works well but not always. Looks like phpMyAdmin has
problems with HTTP post method if I enable my PerlAuthenHandler
Authen.pm. Otherwise phpMyAdmin and Authen.pm work well.
The error I get in phpMyAdmin is:
Fatal error: PMA_sendHeaderLocation called w
Hello all,
Today I tried to limit access to phpMyAdmin using my own Authen.pm
module. It works well but not always. Looks like phpMyAdmin has
problems with HTTP post method if I enable my PerlAuthenHandler
Authen.pm. Otherwise phpMyAdmin and Authen.pm work well.
The error I get in phpMyAdmin is
Thanks All for the valuable suggestions.my $cgi = CGI->new($req); fixed
my issue :)
On Thu, Oct 16, 2008 at 2:04 AM, Perrin Harkins <[EMAIL PROTECTED]> wrote:
> On Wed, Oct 15, 2008 at 2:44 AM, Shibi NS <[EMAIL PROTECTED]> wrote:
> > CGI.pm version 3.15
>
> Update.
>
> - Perrin
>
--
--Shi
On Wed, Oct 15, 2008 at 2:44 AM, Shibi NS <[EMAIL PROTECTED]> wrote:
> CGI.pm version 3.15
Update.
- Perrin
Link::setup_request
>> SetHandler perl-script
>> PerlResponseHandler ARULink::handler
>> PerlOptions +ParseHeaders +GlobalRequest
>> Options ExecCGI
>> AuthNameMetalink
>> AuthTypeBasic
>&g
On Tue, Oct 14, 2008 at 4:28 AM, Shibi NS <[EMAIL PROTECTED]> wrote:
> my $req_params = $req->args;
> my $cgi= CGI->new($req_params);
There's no need to do that. Just call CGI->new(). And make sure you
have the latest version of CGI.pm from CPAN.
- Perrin
Torsten Foertsch wrote:
On Tue 14 Oct 2008, Shibi NS wrote:
And the ARULink::MetalinkAuth::handler is
sub handler
{
my ($req) = @_;
my $status;
my $username;
my $userid;
my $email;
#
# Create a Session object.
#
my $req_params = $req->args;
my $cgi
On Tue 14 Oct 2008, Shibi NS wrote:
> And the ARULink::MetalinkAuth::handler is
>
> sub handler
> {
> my ($req) = @_;
>
> my $status;
> my $username;
> my $userid;
> my $email;
>
> #
> # Create a Session object.
> #
> my $req_params = $req->args;
> my $cgi
ExecCGI
AuthNameMetalink
AuthTypeBasic
PerlAuthenHandler ARULink::MetalinkAuth
require valid-user
ErrorDocument 401 /handle_auth_failure
And the ARULink::MetalinkAuth::handler is
sub handler
{
my ($req) = @_;
Metalink
AuthTypeBasic
PerlAuthenHandler ARULink::MetalinkAuth
require valid-user
ErrorDocument 401 /handle_auth_failure
And the ARULink::MetalinkAuth::handler is
sub handler
{
my ($req) = @_;
my $status;
my $username;
my $userid
Clinton Gormley wrote:
Try adding "warn $msg" statements (instead of printing to a file).
Perl's "warn" function prints to STDERR, which is usually appended to the web
server's errors log. To read the errors as they are printed, do the following (provided
you have shell access on your server,
>
> Try adding "warn $msg" statements (instead of printing to a file).
>
> Perl's "warn" function prints to STDERR, which is usually appended to the web
> server's errors log. To read the errors as they are printed, do the
> following (provided you have shell access on your server, and it's r
was using "SetEnv"
in Apache's .conf file instead of "PerlSetEnv" to set my DBI
variables. Apparently in a PerlResponseHandler, it has access to these
variables, but a PerlAuthenHandler doesn't, so I've just changed those
three lines and it works a treat now.
Th
--- On Wed, 8/20/08, Brett Randall <[EMAIL PROTECTED]> wrote:
> From: Brett Randall <[EMAIL PROTECTED]>
> Subject: Re: Unable to get PerlAuthenHandler to work in mp2
> To: "Perrin Harkins" <[EMAIL PROTECTED]>
> Cc: modperl@perl.apache.org
>
On Wed, Aug 20, 2008 at 5:42 PM, Brett Randall <[EMAIL PROTECTED]> wrote:
> I was wondering about debugging... I'll probably do the good old open a
> file, write to it after each line, and see where it stops writing
No need to open a file. Anything you print to STDERR goes to apache's
error_log,
>>>>> "Perrin" == Perrin Harkins <[EMAIL PROTECTED]> writes:
> On Wed, Aug 20, 2008 at 3:03 AM, Brett Randall <[EMAIL PROTECTED]> wrote:
>> I'm trying to get PerlAuthenHandler to work but when I go to a URL
>> that I've set it up on,
On Wed, Aug 20, 2008 at 3:03 AM, Brett Randall <[EMAIL PROTECTED]> wrote:
> I'm trying to get PerlAuthenHandler to work but when I go to a URL that
> I've set it up on, it asks for a username and password and then lets me
> in no matter what I type.
Have you debugged this
Hey all
I'm trying to get PerlAuthenHandler to work but when I go to a URL that
I've set it up on, it asks for a username and password and then lets me
in no matter what I type.
My entry in Apache'
yway, I think what you are after might be a fully baked AAA (3 httpd
> phases)
> More examples are on perl.apache.org
>
My module works? Am i missing a phase in what I am doing here?
Thanks for all your help BTW.
--
View this message in context:
http://www.nabble.com/PerlAuthenHand
org
Everything below is a snippet of a live site.
vhosts-ssl/site.conf:
- -
~SetHandler modperl
~AuthType Basic
~AuthName "ISST"
~Require valid-user
~PerlAccessHandler ISST::Access
~PerlA
Torsten Foertsch wrote:
>
> On Wed 21 May 2008, fof wrote:
>> I have had problems before when mod_perl seems to override various
>> behavior
>> in Apache. For example when using a PerlAuthenHandler it seemed to wipe
>> out
>> the standard DirectoryIndex di
On Wed 21 May 2008, fof wrote:
> I have had problems before when mod_perl seems to override various behavior
> in Apache. For example when using a PerlAuthenHandler it seemed to wipe out
> the standard DirectoryIndex directive which the main webserver had set to
> index.htm etc. T
fof wrote:
> I am going to try removing the PerlAuthenHandler and simply secure the
> directory with a htpasswd thus taking mod_perl out of the picture. This
> will tell me if some Apache setting in the main server config is being
> inherited by my virtual host and stuffing things
Torsten Foertsch wrote:
>
> On Tue 20 May 2008, fof wrote:
>>
>> PerlAuthenHandler MyAuthenHandler
>> AuthType Basic
>> AuthName "REST Interface"
>> Require valid-user
>>
On Tue 20 May 2008, fof wrote:
>
> PerlAuthenHandler MyAuthenHandler
> AuthType Basic
> AuthName "REST Interface"
> Require valid-user
>
>
> ErrorDocument 401 /http/40
Hello.
I am having a configuration issue trying to use ErrorDocument directive with
a PerlAuthenHandler.
I don't think that this is related to bad mod_perl behavior more likely some
silly configuration error on my part :$ Anyway I am using the centos yum
package install for apache and mod
http://perl.apache.org/docs/2.0/user/handlers/http.html is your friend...
Authen is only called if there is a 'require' and AuthType/AuthName
directive,
Authz is only called if Authen is successful.
Thanks to you both, this does help a lot. In this particular case, I
was only interested in the
see
http://perl.apache.org/docs/2.0/user/handlers/http.html#PerlAuthenHandler
"The check_user_id (authen) phase is called whenever the requested file
or directory is password protected. This, in turn, requires that the
directory be associated with AuthName, AuthType and at least one require
direc
for the record
> Authen is only called if there is a 'require'
that's true
> and AuthType/AuthName
> directive,
but that is not :) you might run into trouble if you don't define those
directives, but their absence won't prevent the auth phases from running.
--Geoff
ging on a newly built server (Apache
2.0.52, mod_perl 2.0.3) and find that both PerlAuthenHandler and
PerlAuthzHandler are ignored. The weird thing is: other Perl*Handlers,
including PerlAccessHandler, work as expected (expected by me, that
is): they block access to mydomain.com/test in the setup c
Martijn wrote:
> Hello.
>
> I'm doing some testing/debugging on a newly built server (Apache
> 2.0.52, mod_perl 2.0.3) and find that both PerlAuthenHandler and
> PerlAuthzHandler are ignored.
>
>
> # PerlAccessHandler TestHandler
> # the above line *does*
Hello.
I'm doing some testing/debugging on a newly built server (Apache
2.0.52, mod_perl 2.0.3) and find that both PerlAuthenHandler and
PerlAuthzHandler are ignored. The weird thing is: other Perl*Handlers,
including PerlAccessHandler, work as expected (expected by me, that
is): they
Am Mittwoch, 16. Mai 2007 16:39 schrieb Joel Bernstein:
> On Wed, May 16, 2007 at 03:28:17PM +0200, Moritz Maisel wrote:
> > Running Debian:
> > libapache2-mod-perl21.999.21-1
> > Integration of perl with the Apache2 web server
>
> So you're running an alpha
On Wed, May 16, 2007 at 03:28:17PM +0200, Moritz Maisel wrote:
> Running Debian:
> libapache2-mod-perl21.999.21-1
> Integration of perl with the Apache2 web server
So you're running an alpha release of mod_perl 2, with 21 levels of
backported patches? Try up
2007/5/15, Adam Prime x443 <[EMAIL PROTECTED]>:
use Apache::RequestRec;
?
I use "Apache::RequestRec" to have access to the object method "user" in the
line:
my $user = $r->user;
What version of mod_perl are you running? The above line makes me thing
you're running an reall old version of m
al Message-
From: Moritz Maisel [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 15, 2007 10:46 AM
To: modperl@perl.apache.org
Subject: apache2 does not deny acces though PerlAuthenHandler returns
HTTP_UNAUTHORIZED
Hi List,
I wrote a PerlAuthenHandler to authenticate users that access a
web
Michael Peters wrote:
> Moritz Maisel wrote:
>
>>Hi List,
>>
>>I wrote a PerlAuthenHandler to authenticate users that access a
>>webservice. I supposed that by returning either "OK" or
>>"HTTP_UNAUTHORIZED" back to apache2 it will allow o
2007/5/15, Michael Peters <[EMAIL PROTECTED]>:
The HTTP codes are HTTP return codes, not handler return codes. Use
FORBIDDEN
instead.
I already tried (and now tried again) to use "return FORBIDDEN" instead of
"return HTTP_UNAUTHORIZED" without success.
:-(
Moritz Maisel wrote:
> Hi List,
>
> I wrote a PerlAuthenHandler to authenticate users that access a
> webservice. I supposed that by returning either "OK" or
> "HTTP_UNAUTHORIZED" back to apache2 it will allow or deny acces due to
> the "require valid-
Hi List,
I wrote a PerlAuthenHandler to authenticate users that access a webservice.
I supposed that by returning either "OK" or "HTTP_UNAUTHORIZED" back to
apache2 it will allow or deny acces due to the "require valid-user"
directive that I set.
My problem is, t
ou use this ->autologin the first argument to
your autologin subroutine will be a string
'MyRoot::Testing'
if you use ::autologin It won't be...
Perhaps this might have something to do with it...
I setup my subroutines like this:-
http.conf
PerlModule MyRoot::Tes
On 3/1/07, Martijn <[EMAIL PROTECTED]> wrote:
But then it still didn't work, until for some reason I changed
PerlAuthenHandler MyRoot::Testing->autologin
to
PerlAuthenHandler MyRoot::Testing::autologin
Don't forget to mark autologin as a method. In mod_perl 2, that
p.conf
PerlModule MyRoot::Testing
PerlAuthenHandler MyRoot::Testing->autologin
===Testing.pm
sub autologin : method
{
my $class =shift;
my $r = shift;
}
--- Martijn <[EMAIL PROTECTED]> wrote:
> As someone here pointed out in an off-list email
> (thanks!), I had
> forgotten
As someone here pointed out in an off-list email (thanks!), I had
forgotten to load the perl module, by writing
PerlModule MyRoot::Testing
in httpd.conf. That wasn't very clever...
But then it still didn't work, until for some reason I changed
PerlAuthenHandler MyRoot::Testing->
Hello.
I've been building a perl script that automatically logs a visitor in
upon visiting the website (given that they're not logged in already
and they have chosen to be remembered by the server etc.).
I've written a handler that does this and I call it using
PerlAuthe
I am getting a similar problem. Its invoking my handler twice for the
same request. I am using PerlAccessHandler.
Thanks
Sumit
Robert Landrum wrote:
Hadmut Danisch wrote:
For some reason the module is called twice for every request.
Is this a HEAD/GET problem? Maybe you're seeing the brows
On Thu, Feb 22, 2007 at 04:18:35PM -0500, Robert Landrum wrote:
> Hadmut Danisch wrote:
> >For some reason the module is called twice for every request.
> >
>
> Is this a HEAD/GET problem? Maybe you're seeing the browser doing a
> HEAD request, then a full GET request?
No, I have checked this
Hadmut Danisch wrote:
For some reason the module is called twice for every request.
Is this a HEAD/GET problem? Maybe you're seeing the browser doing a
HEAD request, then a full GET request?
Rob
detect
subrequests.
Now I do check $r->is_initial_req() to be true and $r->main() to return
undefined/false values, but still get every request twice.
As far as I understood the docs, the PerlAuthenHandler is not called in the
response phase. But what's the reason for being calle
Is it always necessary to declare the perl module as PerlAuthenHandler in
order to update the REMOTE_USER variable. Cant we just define as
PerlHandler and inside the module update the REMOTE_USER.
Currently I am using the following to update the remote user
$r->connection->user
rue -> QueryString is not
present !
In apache I defined my virtualhost like that :
# --
PerlModule Apache2::OK
ServerName rp-name
ProxyPreserveHost On
ProxyPass / http://ip:port/
ProxyPassReverse / http://ip:port/
PerlAuthenHandler Apache2::OK
Require
Frank Wiles wrote:
>
> The best way to think about it is like this:
>
> PerlAccessHandler > is this IP allowed?
> PerlAuthenHandler > is this username allowed?
> PerlAuthzHandler> is this group allowed?
>
Small corre
st
Subject: Re: PerlAuthenHandler, PerlAuthzHandler, Reverse Proxy and Web
Services Problem
On Mon, 8 Jan 2007 17:37:54 +0100
"Sylvain Perrot" <[EMAIL PROTECTED]> wrote:
> First, As I am new to modperl development, I would like to validate my
> configuration :) As I u
On Mon, 8 Jan 2007 17:37:54 +0100
"Sylvain Perrot" <[EMAIL PROTECTED]> wrote:
> First, As I am new to modperl development, I would like to validate my
> configuration :)
> As I understood, PerlAuthenHandler and PerlAuthzHandler are working in
> parallel, and the f
Hi,
I am trying to develop a secured Reverse Proxy which use the
PerlAuthenHandler/PerlAuthzHandler to accept or reject the connection.
The synoptic is the following:
CLIENT -> RP (linux, apache2, modperl) -> Windows Server (.Net
Application, .Net Web Service)
My RP configuration
Perrin Harkins wrote:
That sounds like you aren't even hitting this server. Try shutting it
down and see if you still get a response. You have no other
VirtualHosts in there? Sometimes your request will fail to match the
VirtualHost you expected it to hit and fall through to the default
server
On Tue, 2006-11-14 at 14:40 -0700, Iván Chavero wrote:
> I've comented everything and left only this Location
>
> Alias /prueba /www/imcsk8.example.com/auth
>
> SetHandler perl-script
> PerlResponseHandler NONEXISTENTMODULE
> PerlAuthe
Handler NONEXISTENTMODULE
PerlAuthenHandler NONEXISTENTMODULE
Options +ExecCGI
AuthType Basic
AuthName "The Gate"
Require valid-user
I get no errors on my log files, just the forbidden message on the browser
--
Iván Chavero
Administrador de Sistemas UNIX
CGTI/DSE
Univer
On Tue, 2006-11-14 at 14:16 -0700, Iván Chavero wrote:
> I'm doing tests on a fresh install with one virtual host, here's my
> virtualhost config file:
Try commenting out all of the other Directory, FilesMatch, and Location
blocks. Also, try changing PerlResponseHandler for that block to
somethi
Perrin Harkins wrote:
On Tue, 2006-11-14 at 12:34 -0700, Iván Chavero wrote:
I even changed the PerlAuthenHandler value to a non existent module
(which i think it should give a startup error) and it gets ignored.
That sounds like a config problem to me. I bet you have another
mod_perl 2 :)
AuthType Basic
AuthName "BAR"
Require valid-user
PerlAccessHandler AAA::Access
PerlAuthenHandler AAA::Authen
PerlAuthzHandler AAA::Authz
http://perl.apache.org/docs/2.0/user/handlers/http.html#PerlAuthenHandler
Note that part syaing you need at least 1 require
On Tue, 2006-11-14 at 12:34 -0700, Iván Chavero wrote:
> I even changed the PerlAuthenHandler value to a non existent module
> (which i think it should give a startup error) and it gets ignored.
That sounds like a config problem to me. I bet you have another
Location block that is apply
Philip M. Gollucci wrote:
> Michael Peters wrote:
>>
>> Iván Chavero wrote:
>>
>>> my mod_perl copile flags are this:
>>>
>>> perl Makefile.PL MP_APXS=/usr/local/apache-2.2.2/bin/apxs
>>
>> you need EVERYTHING=1 there, or specifically turn on PERL_AUTHEN,
>> PERL_AUTHZ,
>> PERL_ACCESS individuall
AuthName "BAR"
Require valid-user
PerlAccessHandler AAA::Access
PerlAuthenHandler AAA::Authen
PerlAuthzHandler AAA::Authz
http://perl.apache.org/docs/2.0/user/handlers/http.html#PerlAuthenHandler
Note that part syaing you need at least 1 require
Iván Chavero wrote:
> my mod_perl copile flags are this:
>
> perl Makefile.PL MP_APXS=/usr/local/apache-2.2.2/bin/apxs
you need EVERYTHING=1 there, or specifically turn on PERL_AUTHEN, PERL_AUTHZ,
PERL_ACCESS individually.
--
Michael Peters
Developer
Plus Three, LP
executed.
I don't know if i'm doing something wrong because even with LogLevel to
debug i don't get error messages on the apache log files; it seems as if
PerlAuthenHandler is being ignored.
This is how i am loading the handler:
... Alias /Dau /www/virtual_1/Dau AuthName Omni
;
> get_basic_auth_pw and note_basic_auth_failure
>
> which can not be found ..
>
>
> ...
> AuthName Database
> AuthType Basic
> PerlAuthenHandler Xdb::AuthOra2->handler
> require valid-user
> PerlResponseHandler Xdb::ApacheDB-&g
Hi,
I'm trying to migrate from MP1 to MP2 and having trouble with
get_basic_auth_pw and note_basic_auth_failure
which can not be found ..
...
AuthName Database
AuthType Basic
PerlAuthenHandler Xdb::AuthOra2->handler
require valid-user
PerlResponseHan
Tyler MacDonald wrote:
That looks great to me. If getLoggedIn() doesn't have any side
effects (such as setting $r->user), you could also make it a tiny tiny bit
faster by removing the "my $user" line above, and changing this:
Good catch thanks. Brain dead moment.
--
---
Philip M. Gollucci <[EMAIL PROTECTED]> wrote:
> sub handler {
> my $r = shift;
>
> my $user = ISST::User->getLoggedIn($r);
>
> ## IS THIS CORRECT ?
> ## can't used DECLINED or you get the REALM popup
> return Apache2::Const::OK if $r->uri =~
> m#/timeline/(login|logout|r
AuthName "ISST"
Require valid-user
PerlAccessHandler ISST::Access
PerlAuthenHandler ISST::Authen
PerlAuthzHandler ISST::Authz
Here's the ISST:Authen code --- See the commented question in it. Thanks!
sub handler {
my
>It also makes no difference if I move the .htaccess file out of the
> way and put the directives into a clause in the server
> config.
if you can do a quick setup using
http://people.apache.org/~geoff/bug-reporting-skeleton-mp2.tar.gz
I'd be happy to look at it. otherwise, it's been pu
> > ==
> > PerlAccessHandler GML::Reporter
> > PerlAuthenHandler GML::Reporter
>
> your authen handler ought to be setting $r->user to some meaningful value.
> it probably won't affect things, but add it anyway :)
The real code does set this (i
offhand I don't see the problem immediately. but here are some questions
> ==
> PerlAccessHandler GML::Reporter
> PerlAuthenHandler GML::Reporter
your authen handler ought to be setting $r->user to some meaningful value.
it probably won't affect thi
-8<-- Start Bug Report 8<--
1. Problem Description:
Has anyone managed to get a PerlAuthenHandler to work with
mod_perl2.0.2?
I'm having problems getting PerlAuthenHandler to work in a .htaccess
file. It gets called, but then *all* other
Geoffrey Young wrote:
>
>
> Bengt-Arne Fjellner wrote:
>> Hi. Im working on a modperl login module that amongst others will check for
>> https
>> If not https I want to give an error page instead.
>
> you'll need something like Apache::SSLLookup to determine https during the
> authen phase.
Than
lly thinking about the request cycle properly. if
you want to enforce https you probably ought to use a PerlAccessHandler and
return FORBIDDEN unless https and push a PerlAuthenHandler otherwise, then
use the authentication phase for what it's for - authenticating your user.
if you wa
Hi. Im working on a modperl login module that amongst others will check for
https
If not https I want to give an error page instead.
Is it possible to return html from an authen handler ?
How?
Is it possible to create a temporary ... from this
handler?
Or give an internal_redirect directly to c
Geoffrey Young wrote:
$r->set_handlers(PerlAuthenHandler => [\&OK]);
this is the correct approach - OK means "I authenticated" and lets apache
know that it should _not_ call mod_auth.
however, the symbol OK doesn't exist in your setup, so you are essentially
passing undef
> and I've tried all of the following to overide the AuthenHandler
>
> $r->set_handlers(PerlAuthenHandler => []);
> $r->set_handlers(PerlAuthenHandler => undef)
those only remove the PerlAuthenHandler from the handler chain. that is,
since you probably have mod_aut
Hi everyone.
I think I only have 2 hurdles left to get my mp1 stuff running under mp2
I have an access handler that overrides my PerlAuthenHandler for a
couple of locations:
Here's the accesshandler:
use Apache::Constants qw(OK);
use strict;
use warnings;
sub handler {
my $r =
Ferrari Geoffrey wrote:
> Hi,
>
> If I have activated a PerlAuthenHandler for a directory in httpd.conf with
>
>
> ...
> PerlAuthenHandler My::Handler
>
>
> How can I deactivate this PerlAuthenHandler for a subdirectory, such as
> /foo/bar ?
if you wan
1 - 100 of 117 matches
Mail list logo
