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
-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
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
of a
On Tue, May 01, 2001 at 01:58:56PM -0400, Chris Strom wrote:
I can't say as I've had any problems using
err_headers_out-add(Set-Cookie) with any browsers. I'm
surprised to hear that you've had problems with it.
even DURING a redirect? i seem to have hit a chord here, as
i'm
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
Hi. Sometimes, one has to answer one's own questions
On Fri, Mar 30, 2001 at 03:00:08PM +0200, Jochen Schnapka wrote:
Hi.
I'm trying some of the well-known Apache-Perl-Modules, such as
DayLimit.pm.
Strangely, the server throws an internal error (500), when the Perl module
returns 'OK'.
#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.
09, 2001 11:44 AM
To: Joseph Crotty
Cc: '[EMAIL PROTECTED]'
Subject: Re: PerlAccessHandler Question...
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.
14 matches
Mail list logo