Once upon a time there was a project that required a PerlAccessHandler
and form-based login. This project lived in the land of mod_perl, so it
lived a happy life, with a setup something like:
Location /not-protected
PerlHandler Apache::Registry
SetHandler perl-script
Options +ExecCGI
On Fri, Jul 26, 2002 at 04:11:29PM -0700, Rasoul Hajikhani wrote:
Folks,
My PerlAccessHandler is being executed twice per each request. Is this a
normal behavior for an access handler?
Here is my .conf entry
Location /myHandler
SetHandler perl-script
# run is a wrapper
Authentication, and have trouble in
setting
PerlAccessHandler
PerlAuthenHandler
etc.
If I put
###==
Location /mpl/hello
SetHandler perl-script
PerlHandler Apache::Hello
/Location
###==
in the perl.conf file, it's ok. I got the expected from
Folks,
My PerlAccessHandler is being executed twice per each request. Is this a
normal behavior for an access handler?
Here is my .conf entry
Location /myHandler
SetHandler perl-script
# run is a wrapper for my handler
# all common methods which many of my handlers
I'm a verteran CGIer but a new mod-perl user.
I have got the mod-perl running fine for the content handling. But when I
try to step in to other stages like Authentication, and have trouble in
setting
PerlAccessHandler
PerlAuthenHandler
etc.
If I put
###==
Location /mpl/hello
When I put a PerlAccessHandler inside a LimitExcept, it does not seem to
work within the LimitExcept. It behaves as if there was no LimitExcept.
For instance, I wrote a simple access handler for webdav that only allows
users into their own directories. So user joe can only get to
/home/joe
-Original Message-
From: will trillich [mailto:[EMAIL PROTECTED]]
thanks one and all for the pointers on cookies. i probably grok
738% more than i did, but i have a feeling it's still only 13% of
the pie. or in this case, cookie...
so how's this PerlAccessHandler, for twisted
will trillich said...
problem: some browsers see 'redirect' and ignore all other
headers, so the cookies aren't set. when the browser arrives at
the login area, there's no cookie to send there, to formulate
a return-to address from.
What percentage of 'some browsers' is your user
thanks one and all for the pointers on cookies. i probably grok
738% more than i did, but i have a feeling it's still only 13% of
the pie. or in this case, cookie...
so how's this PerlAccessHandler, for twisted logic? hole-punching
and pitfall-warning equally welcome:
#httpd.conf
Chris Strom wrote:
-Original Message-
From: will trillich [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 30, 2001 9:44 PM
To: [EMAIL PROTECTED]
Subject: PerlAccessHandler -- struggling and drowning
this is a PerlAccessHandler, which should check for the existence
getting lots of me too in my mailbox.
Even during a redirect. The following works for me (in a PerlInitHandler
NOT a PerlAccessHandler) with lynx (2.7) just fine.
$r-err_headers_out-add('Location' = $dest);
$r-err_headers_out-add('Set-Cookie' = $cookie);
$log-debug(Authentication
headmeta http-equiv=Refresh content=2;
http://www.no-way-in-hell-bubba.com/login/;
should be:
meta http-equiv=Refresh content=2;
URL=http://www.no-way-in-hell-bubba.com/login/;
On Tue, May 01, 2001 at 02:49:05PM -0400, Chris Strom wrote:
headmeta http-equiv=Refresh content=2;
http://www.no-way-in-hell-bubba.com/login/;
should be:
meta http-equiv=Refresh content=2;
URL=http://www.no-way-in-hell-bubba.com/login/;
tolja my understanding was questionable.
On Tue, May 01, 2001 at 01:39:13PM -0500, will trillich wrote:
On Tue, May 01, 2001 at 01:58:56PM -0400, Chris Strom wrote:
Even during a redirect. The following works for me (in a PerlInitHandler
NOT a PerlAccessHandler) with lynx (2.7) just fine.
$r-err_headers_out-add('Location
will trillich ([EMAIL PROTECTED]) said something to this effect on 05/01/2001:
now when lynx or netscape (but not konqueror) get validated, and
the server tries to redirect the browser back to the original
URL, the browsers seem to have cached the /login page as if it
were the /protected
-Original Message-
From: will trillich [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 01, 2001 3:38 PM
To: [EMAIL PROTECTED]
Subject: Re: PerlAccessHandler -- struggling and drowning
now when lynx or netscape (but not konqueror) get validated, and
the server tries
.
this is a PerlAccessHandler, which should check for the existence
of a cookie in the incoming headers, and if not there (or
expired) it should redirect the browser to a login area that
takes name/password pair, and if valid, would then return the
browser to the original URL. to do that, as we issue
'. The same is with 'DECLINED'.
FORBIDDEN works well, AUTH_REQUIRED works also (though it doesn't make
sense in the access control stage).
I do not see anything in my error_log.
The problem seems to be specific to the PerlAccessHandler
Other Handlers (e.g.the PerlAuthenHandler) work fine: when
stage).
I do not see anything in my error_log.
The problem seems to be specific to the PerlAccessHandler
Other Handlers (e.g.the PerlAuthenHandler) work fine: when returning OK,
the page is displayed.
Any ideas?
Info: apache-1.3.19, mod_perl-1.25, perl5.005_03, OS: BSD/OS 4.1
Greetings
#Location Handlers
Location
PerlAccessHandler Apache::GateKeeper
/Location
The Location directive needs to specify a URL to which it applies:
Location /
Perl*Handlers can go pretty much anywhere, as long as the server
administrator hasn't diabled .htaccess files
Hi there,
On Tue, 9 Jan 2001, Joseph Crotty wrote:
open(FILE, "/tmp/dog");
Always check the status returned by a call like open().
73,
Ged.
Good advice Ged. I figured out the problem...there was another server
running on the port almost exactly like the one I was using, but without the
PerlAccessHandler. Huge brain fart. I need a nap.
-Original Message-
From: G.W. Haywood [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January
On Thu, 28 Sep 2000, Adi wrote:
As it turns out, the second call to My::ProxyAccessOnly is an internal
redirect
...
Is there a logical reason why PerlAccessHandler should be called twice, the
because internal_redirects are implemented with subrequests and
subrequests run all phases (except
PerlPostReadRequestHandler runs
before PerlAccessHandler, so $r-remote_addr has already been changed to the
client's IP.
So, I wrote my own PerlAccessHandler that reads $r-notes to see if the request
came from the proxy:
Perl
sub My::ProxyAccessOnly {
my $r = shift;
my $from_proxy = $r-notes
Hello.
I just compiled mod_perl-1.21 with: perl Makefile.PL EVERYTHING=1
When I try to use the PerlAccessHandler directive in my httpd.conf
I get:
Invalid command 'PerlAccessHandler', perhaps mis-spelled or defined by a
module not included in the server configuration
When the Makefile.PL
I'm experiencing the same problem and looking for help.
Miguel Navarro
[EMAIL PROTECTED]
--
From: Einar Johnsson
Sent: Friday, November 05, 1999 6:51 AM
To: [EMAIL PROTECTED]
Subject: Problems parsing PerlAccessHandler directive...
Hello.
I just compiled mod_perl-1.21 with: perl
26 matches
Mail list logo
