documentation here:
http://httpd.apache.org/docs-2.0/mod/mod_include.html
> So this is my question. Are perlhandlers better than CGI registry scripts in
> speed but not in funcionality???
Perl handlers have better speed and functionality than CGI scripts
running under Registry, but that has no
But it seems to be that with modperl as DSO this directive does not work,
and that Apache::include is only a modperl1.x funcionality, so discarted in
mod perl 2.
I've started this port, but it's a long way from being completed - it
doesn't work right and dumps core, but I haven't looked at it i
I began some weeks ago to think about translating my .pl scripts (that run
with mod_perl 2 ::registry) to perl handlers.
My first problem was to find how to include a perl handler as i included my
cgi scripts (include virtual).
I found that #perl directive allows you to include with Apache
Cees Hek wrote:
[chomp]
Thanks Cees, that's exactly what I needed :) My stuff is all completely
generated by scripts where I need access control, but I certainly
see the use for controlling static entity access.
Carl
n.
>
> At present I've knocked up a site that does auth via a
> form and state tracking with Session.pm. The form checks
> usernames & passwords against a MySQL database, and the state is
> maintained by Session. This seems quite logical to me, coming from
> essentially
state tracking with Session.pm. The form checks
usernames & passwords against a MySQL database, and the state is
maintained by Session. This seems quite logical to me, coming from
essentially a CGI background, but the discussion of handlers
around here makes me believe there's a b
After a few fruitless days of fiddling with this, I find myself getting
nowhere... Can anyone really explain how Apache::ReadConfig and/or direct
me to the source code (for handling the namespace, not the code for
sections)
Issac
- Original Message -
From: "Perrin Harkins" <[EMAIL PROTECTED]>
> On Mon, 2003-06-02 at 15:19, Issac Goldstand wrote:
> > No - this is at startup. It's also, to the best of my knowledge, the
*only*
> > way to push handlers onto a dynamic URL (eg, wher
On Mon, 2003-06-02 at 15:19, Issac Goldstand wrote:
> No - this is at startup. It's also, to the best of my knowledge, the *only*
> way to push handlers onto a dynamic URL (eg, where the URL is a variable) -
> which is what I'm trying to do.
I was referring to the $r->push
> PerlHeaderParserHandler => sub {$self->some_other_method;}
> > };
> >
> > But when I browse to /some/URL, some_other_method never gets called, let
> > alone by $self
>
> What are you trying to do? You know you can only do this sort of thing
> during server s
> alone by $self
What are you trying to do? You know you can only do this sort of thing
during server startup, right? After startup, you can still push
handlers but you have to do it differently.
- Perrin
I want to assign a method handler from within the Apache::ReadConfig
namespace. Right now, what I have is some function which somewhat
resembles:
package My::Object;
sub method1 {
my $self=shift;
package Apache::ReadConfig;
no strict;
$Location{'/some/URL/'} = {
Options => '+ExecCGI',
P
I'm looking at Apache::SessionX from Embperl as a possible
session tracker for an app I'm doing with Template::Toolkit,
has anyone any comments/suggestions re how mature this,
(or any other recommendations?) session tracking module
is under mp2? I've read some comments on CPAN discussing
the use
Hi There,
I read the following thread (with Geoff's comment in there too):
http://www.gossamer-threads.com/archive/mod_perl_C1/docs-dev_F5/a_little_feedback_P38941/
than I thought about Geoff's advice about using PerlAccess Handler and
came
up with this concoction (which works :-) )
Conf entry:
A
I tried that already. When I use PerlAccessHander with Satisfy Any, the
webpage is always served even if IP check fails. Interestingley, when IP
check fails, it redirects (https url) but never ask for any userid or
password and straight away serves the page.
--
Shashank
On Fri, 30 May 2003, Geoff
When http://www.abc.com/~xyz gets called PerlAuthenHandler MyModule is
invoked. MyModule code checks for IP after reading a file from xyz
directory.
If the host ip matches with the one in the file, it returns OK and the
PerlAuthzHandler never gets called and the webpage is served to the user.
you
I try to do the following:
Outside the virtual host (non-ssl) in the location directive, I have the
following:
AuthName someauth
AuthType sometype
PerlAuthenHandler MyModule
require valid-user
When http://www.abc.com/~xyz gets called PerlAuthenHandler MyModule is
invoked. MyModule code checks fo
[EMAIL PROTECTED] wrote:
thnx for your reply.
I use mod_perl 2 (1.99_08) and CGI.pm 2.91 and Apache 2.0.44. I thought that CGI.pm
wouldnt work at all, so I didnt give any examples.
I wrote a simply script that checks if running under mod_perl,
displays some parameter and evaluates/presents a f
GI.pm does just not work inside an apache-handle.
For the docs of mod_perl-handlers I read perl.apache.org, but I
couldnt find any tutorials about writing handlers in
mod_perl. Especially a description about the methodes and values of
the responsehandler-object.
thnx a lot, peter
the source:
Hi!
On Wed, Apr 02, 2003 at 12:49:56AM +0200, [EMAIL PROTECTED] wrote:
> Is the O'Reilly about apache-modules what I'm looking for ? I've the
> small O'reilly about mod_perl but it raises more questions than its
> answers.
The "Eagle" book is definitly very interesting (if a little bit old - B
[EMAIL PROTECTED] wrote:
I used CGI.pm in my mod_perl-application to get 'path_info', 'param',
print out headers and more.
None of this works inside my own handlers any more.
Which mod_perl generation are you using? mod_perl 1.0 (1.27?) or mod_perl 2.0
(1.99_08?). I susp
While I'm programming mod_perl for quite a while now I only recently
discovered the wonders of writing my own apache-handlers.
I used CGI.pm in my mod_perl-application to get 'path_info', 'param',
print out headers and more.
None of this works inside my own handler
On 13 Mar 2003 at 5:16, [EMAIL PROTECTED] wrote:
> Hi -
>
> I'm a rookie; I'm developing a handler under
> mod_perl 1.99-09-dev (cvs) and Apache 2.0.44.
>
> The handler works w/o subs; but when I split
> it up with 'local' subroutines, as:
>
> [...]
*STUPID*STUPID*STUPID*STUPID*STUPID*STUPID*
03] [error] [client ::1]
Undefined subroutine
&MyApache::Redirect::process_ssl called at
/srv/www/perl/MyApache/Redirect.pm line 36.
I'm missing something kind of basic here, but
the examples on the mp2 site show handlers
with subroutines (Eagle book too).
Aloha => Beau;
On Wed, 19 Feb 2003, Nick Tonkin wrote:
>
> Hi all,
>
> Cookies driving me nuts as usual but I think the problem appears to be
> related to which handler phase we are in.
>
> Basically, the same call to read the cookies works in the PerlHandler but
> not in the PerlAccessHandler.
Responding to my
I had some handlers that did not explicitly return OK -- just printed the
coontent and quit. In apache1/mp1 this 'worked' fine.
After migrating to apache2/mp2 these handlers delivered the content to the
browser but then printed a 500 error message to the browser but _not_ to
the error
Hi all,
Cookies driving me nuts as usual but I think the problem appears to be
related to which handler phase we are in.
Basically, the same call to read the cookies works in the PerlHandler but
not in the PerlAccessHandler.
in Access.pm I have :
use CGI;
use CGI::Cookie;
sub handler {
my
Iñaki Martínez wrote:
Hi!!!
Well this is my firts post in this list...
I have a server with several domains which each of them has its own
handlers, subroutines and there are several common subrutines.
What i want to do it is organize the directory structure, so:
/modperl
Hi!!!
Well this is my firts post in this list...
I have a server with several domains which each of them has its own
handlers, subroutines and there are several common subrutines.
What i want to do it is organize the directory structure, so:
/modperl/domain_1/
/modperl
Yes, with the newest cvs, it works like expected!
Thank you all for your help!
Helmut
--On Mittwoch, 29. Januar 2003 12:05 +1100 Stas Bekman <[EMAIL PROTECTED]>
wrote:
Try again with the current cvs. You can look at the test
t/hooks/TestHooks/stacked_handlers.pm which aborts the execution chai
however, DONE is special - it indicates that all content has been sent
and the request cycle should proceed straight to the logging phase.
from a handler perspective, DONE behaves the same as an error code -
it terminates the request cycle.
But the book doesn't say that DONE does break the
Geoffrey Young wrote:
First of all let's clear up the 1.0 side:
Quoting the eagle book:
The exception to this rule [all handlers will run] is if one of
the handlers in the series returns an error code (anything other than
OK, DECLINED, or DONE)
Though the code does *not* chec
First of all let's clear up the 1.0 side:
Quoting the eagle book:
The exception to this rule [all handlers will run] is if one of
the handlers in the series returns an error code (anything other than
OK, DECLINED, or DONE)
Though the code does *not* check for DONE:
mod_perl.c
Try again with the current cvs. You can look at the test
t/hooks/TestHooks/stacked_handlers.pm which aborts the execution chain when
Apache::DONE is returned.
__
Stas BekmanJAm_pH --> Just Another mod_perl Hacker
htt
Geoffrey Young wrote:
Helmut Zeilinger wrote:
Hi,
i am using mod_perl 1.99_08.
I have two mod_perl handlers:
...
PerlResponseHandler Test::handler0 Test::handler1
...
How can i brake the execution chain between handler0 and handler1?
Whatever i try as handler0 return value (OK, DECLINED
Helmut Zeilinger wrote:
Hi,
i am using mod_perl 1.99_08.
I have two mod_perl handlers:
...
PerlResponseHandler Test::handler0 Test::handler1
...
How can i brake the execution chain between handler0 and handler1?
Whatever i try as handler0 return value (OK, DECLINED, FORBIDDEN, 404)
the
Hi,
i am using mod_perl 1.99_08.
I have two mod_perl handlers:
...
PerlResponseHandler Test::handler0 Test::handler1
...
How can i brake the execution chain between handler0 and handler1?
Whatever i try as handler0 return value (OK, DECLINED, FORBIDDEN, 404)
the
handler1 is still executed
[please always reply to the list! thank you!]
Randy J. Ray wrote:
I guess Philippe can comment on the sections part, I think it
should be in RSN. What about method handlers? What's wrong with them?
Only that my handlers, both prototyped as ($$), received only the
request object (A
is by installing those).
I guess Philippe can comment on the sections part, I think it should
be in RSN. What about method handlers? What's wrong with them?
__
Stas BekmanJAm_pH --> Just Another mod_perl Hacker
http
Any indication of when/if these features will make it to mp2? I've been trying
to get my RPC::XML code (specifically the Apache::RPC::Server and
Apache::RPC::Status modules) to work under Apache2 and mod_perl2 (thanks to
Red Hat for pushing up my timetable on this by installing those).
Randy
--
So I converted Util::Tour::Translate's handler into a regular non object
handler and everythings works fine. I would rather use object handlers but
this doesn't seem possible if a content handler is performing an
internal_redirect which might invoke that handler.
this has been repor
fined subroutine
&Util::Tour::Translate->handler::handler called at
/home/www.website.com/lib/Util/Tour/Banner.pm line 66.
So I converted Util::Tour::Translate's handler into a regular non object
handler and everythings works fine. I would rather use object handlers but
this doesn&
On Wed, 2003-01-15 at 14:24, Geoffrey Young wrote:
> if you want to force %ENV to be setup earlier, try calling
>
> $r->subprocess_env;
>
> in a void context before checking %ENV - it used to segfault for me, but the
> docs says it should work.
>
This worked for me! Thanks a million!
-vish
But, I'm not able to see that cookie when I print $ENV{'HTTP_COOKIE'}
within in header_parse_handler.
%ENV is setup during the fixup phase, so it hasn't been populated yet.
mod_perl docs say that that you can
examine request headers in the PerlHeaderParserHandler.
yes, using something like
Hi,
I'm unable to access/read cookies from incoming HTTP requests using
mod_perl HTTP request handlers.Here's what my relevant apache config
section looks like
PerlHeaderParserHandler MyModule::header_parse_handler
My browser already has a cookie named 'foo' with value 'bar' with path
SB> Geoffrey Young wrote:
>> Ruslan U. Zakirov wrote:
>>> Hello All!
>>> Short synopsis:
>>> How to push handler just after handler that working now?
>>> More about the problem.
>>> I've got main handler, that forms stack of h
Geoffrey Young wrote:
Ruslan U. Zakirov wrote:
Hello All!
Short synopsis:
How to push handler just after handler that working now?
More about the problem.
I've got main handler, that forms stack of handlers from query
string
by calling push_handlers(). Then each module doin
Ruslan U. Zakirov wrote:
Hello All!
Short synopsis:
How to push handler just after handler that working now?
More about the problem.
I've got main handler, that forms stack of handlers from query string
by calling push_handlers(). Then each module doing his job. Some handlers
Hello All!
Short synopsis:
How to push handler just after handler that working now?
More about the problem.
I've got main handler, that forms stack of handlers from query string
by calling push_handlers(). Then each module doing his job. Some handlers
needs to put another hook
On Wed, Dec 04, 2002 at 11:37:20AM +0200 /me wrote:
> I am having trouble setting different Perl*Handler's for two different
> VirtualHosts. The virtual hosts use one IP and are name-based.
[... details skipped ...]
It works. It was me that's wrong. PerlFixupHandlers work just as
expected with nam
orrectly, but
> after that test1.domain invoces App1001::Setup again.
>
> Is this as designed? Is it possible to run multiple applications with
> different Perl*Handlers using virtual hosts? Any readings I've missed?
>
>
> Thanks in advance.
> dam
omain after that - I get App1::Setup invoked,
instead of App1001::Setup
after a restart I am able to work with test1001.domain correctly, but
after that test1.domain invoces App1001::Setup again.
Is this as designed? Is it possible to run multiple applications with
different Perl*Handlers using vi
attribute is implemented, but what
I was trying to do was create a :Profiled attribute handler.
ah. :method is implemented in Perl core, while Attribute::Handlers is
not - see the attributes manpage for a list of built-in attributes.
I tried just putting a CHECK block with a warn in my
what
I was trying to do was create a :Profiled attribute handler. So in my
base class I had:
use Attribute::Handlers;
sub Profiled ATTR(CODE) { ... }
and in a subclass:
sub foo :Profiled {
}
but I was never able to get the Profiled handler to get called. I
looked into Attribute::Handlers
Michael Schout wrote:
Geoffrey Young wrote:
keep in mind that neither book mentions the use of subroutine
attributes, which is allowed in 1.3 but the only way in 2.0
sub handler : method {
...
}
I am 99% sure that Attribute handlers wont work in 1.3 because
Attribute::Handlers use
Geoffrey Young wrote:
keep in mind that neither book mentions the use of subroutine
attributes, which is allowed in 1.3 but the only way in 2.0
sub handler : method {
...
}
I am 99% sure that Attribute handlers wont work in 1.3 because
Attribute::Handlers use CHECK{} blocks to set up the
e probably discovered, you're using a feature called 'method
handlers' and you should be able to find examples in the eagle book as
well.
keep in mind that neither book mentions the use of subroutine
attributes, which is allowed in 1.3 but the only way in 2.0
sub handler : method {
"Richard Clarke" <[EMAIL PROTECTED]> wrote:
>Now I feel stupid. $sub->handler was supposed to be "$sub->handler".
>
>That's what you get for being impatient.
or perhaps `sub { $sub -> handler(@_) }' -- if quoting works,
great, but I would fear that "$sub->handler" would stringify before
push_handl
L PROTECTED]>
Sent: Wednesday, November 06, 2002 4:08 PM
Subject: Re: OO handlers
> I should add that this segv only happens when using push_handlers like
> below. If I put Control::Super::Sub->handler inside a tag in
> httpd.conf then it is fine.
>
> Ric
>
> - Original
nesday, November 06, 2002 3:55 PM
Subject: OO handlers
> List,
> Tired of having 10 modules all with near identical handler methods I
> decided to put the handler method into a superclass and be done with
> maintaining the same code 10 times. I first tried this a couple of weeks
ag
looks like
sub handler ($$) {
my $self = shift;
my $r = Apache::Request->instance(shift);
# do stuff
}
Testing this with httpd -X causes a segfault every time I go to the URL. So
my question is, before I try to figure out why it segv's, is this kind of
thin
Ruslan U. Zakirov wrote:
Hi!
Please point me to good documentation about subj.
Is it possible to initialize some class(MyProjConfig for example)
with some params in first content handler, and then send it trought
other handlers, all it within only one request?
see $r->pnotes() in man Apa
t
RUZ> other handlers, all it within only one request?
RUZ> Thank you beforehead.
RUZ> __
RUZ> Sorry for my English.
see:
http://perl.apache.org/doc
Hi!
Please point me to good documentation about subj.
Is it possible to initialize some class(MyProjConfig for example)
with some params in first content handler, and then send it trought
other handlers, all it within only one request?
Thank you beforehead
Hi everyone.
I've revisited using Attribute::Handlers work under mod perl again, and I am
still unsuccesful.
Looking at Attribute::Handlers, it appears that Attribute::Handlers relies
on CHECK blocks to do its work. I verified this by uncommenting one of the
debugging warnings in Handle
Hi.
If I do an internal redirect, will there be a call to the initial requests
cleanup handler?
Of course I could test this but I would prefer documented behaviour. Is
this written anywhere?
Thanx,
Joachim
--
"... ein Geschlecht erfinderischer Zwerge, die fuer alles gemietet werden
koennen.
Stas Bekman wrote:
>
> Pete Rothermel wrote:
> > I've got the example echo() handler working for a non-HTTP protocol as
> > outlined on the new web site:
> >
> >
>http://perl.apache.org/docs/2.0/user/handlers/handlers.html#Command__Protocol__Phases
>
Pete Rothermel wrote:
> I've got the example echo() handler working for a non-HTTP protocol as
> outlined on the new web site:
>
> http://perl.apache.org/docs/2.0/user/handlers/handlers.html#Command__Protocol__Phases
>
> Anybody have a similar example for the same pr
I've got the example echo() handler working for a non-HTTP protocol as
outlined on the new web site:
http://perl.apache.org/docs/2.0/user/handlers/handlers.html#Command__Protocol__Phases
Anybody have a similar example for the same protocol handler over SSL?
thanks
Pete Rothermel
On Fri, 3 May 2002, Peter Rothermel wrote:
> I tried the mehod attribute and now I get this error:
>
> Error message:
>Can't locate object method "" via package "Apache::AuthDerivedHandler".
method handlers were broken in _01, this has been fixed in cvs and will be
in 1.99_02
Jeff AA wrote:
>>Try per load the class my::class via startup.pl or PerlModule
>>
>
> I already had PerlModule my::classes in httpd.conf
> Tried PerlRequire as well - still the same error
the steps are outlined pretty well in recipe 10.3 (since you mentioned the cookbook
earlier). from the
May 2002 09:58
To: Jeff AA
Cc: [EMAIL PROTECTED]
Subject: Re: unable to use method type handlers?
Try per load the class my::class via startup.pl or PerlModule
Tor.
Jeff AA wrote:
>
> Whenever I try to set up a method type handler
>
> PerlHandler my::classes->mymethod
>
Try per load the class my::class via startup.pl or PerlModule
Tor.
Jeff AA wrote:
>
> Whenever I try to set up a method type handler
>
> PerlHandler my::classes->mymethod
>
> I get the following in the error log:
>
> Undefined subroutine &my::classes->mymethod::handler called.
>
> usin
Whenever I try to set up a method type handler
PerlHandler my::classes->mymethod
I get the following in the error log:
Undefined subroutine &my::classes->mymethod::handler called.
using:
Apache/1.3.23 (Unix) Debian GNU/Linux
mod_perl/1.26 mod_ssl/2.8.7 OpenSSL/0.9.6c
any hints would
I tried the mehod attribute and now I get this error:
Error message:
Can't locate object method "" via package "Apache::AuthDerivedHandler".
Geoffrey Young wrote:
> Peter Rothermel wrote:
>
> > Can somebody help me out with Method Handlers in
&g
Peter Rothermel wrote:
> Can somebody help me out with Method Handlers in
> Apache2 - mod_perl 1.99? I'm new to windows and its
> threading issues.
[snip]
> sub authenticate ($$) {
> my ($self, $r) = @_;
> return OK;
> }
I haven't played much with mo
Can somebody help me out with Method Handlers in
Apache2 - mod_perl 1.99? I'm new to windows and its
threading issues.
Here's a simple authentication handler that shows where
I'm getting stuck. I need to initialize a AuthDerivedHandler
object but I'm not sure exactly how
Hello!
How to enable only PerlSetVar/PerlAddVar directives in .htaccess files?
More specific:
We are building an multiuser environment with mod_perl to our
campus. Mod_perl handlers contain especially PerlHandlers configured in
httpd.conf. The .htaccess files are used for
On Fri, Mar 29, 2002 at 11:34:26AM -0600, Michael Schout wrote:
> Has anyone else tried to use Attribute::Handlers under mod_perl? Any success
> stories?
Take a look at Apache::Handlers :)
I've been able to get both forms working (attribute and block).
Attribute::Handlers does r
I made an attempt to use Attribute::Handlers under mod perl today, and it
appears that this cant be done. What I was hoping to do was use
Attribute::Deprecated, and Attribute::Profiled in my perl handlers.That way
I could say something like:
package MyHandler;
sub whatever : Profiled
Hans Poo wrote:
> Please Help
>
> One of my handlers do an:
>
> $r->set_handlers( PerlInitHandler => undef);
>
> Later in the same virtual host configuration there is another Directory
> covering the URL / with this handler.
>
> PerlInitHandler
Please Help
One of my handlers do an:
$r->set_handlers( PerlInitHandler => undef);
Later in the same virtual host configuration there is another Directory
covering the URL / with this handler.
PerlInitHandler "sub { my $r = shift; warn 'callback', $r->curre
Nico Erfurth wrote:
> your handler could tie the output-handle (is this possible?) and run a
> subrequest.
Nope, not possible. You can only do that for mod_perl requests.
- Perrin
Andy Lester wrote:
> How can I get mod_perl to handle all Apache output, whether or not it
> originates with mod_perl?
>
> I'm writing a module that needs to analyze all output generated by Apache.
> That's easy enough with stacked handlers, but I'm goofing somethi
As far as I understand, it should be a chain of handlers. It's very close to
one of my current projects. You have to serve one of the early stages of the
request to decide what handler is appropriate for the content generation
phase in particular conditions, and dynamically install that ha
Andy Lester wrote:
> So, my HTML::Lint checking is only going to work on output from the
> mod_perl chain.
If you aren't terribly concerned about performance, there are several
Apache::Proxy modules which should be easy to modify to put your lint
checking in. Do a search for "proxy" on CPAN to
look at the generated content from
> non-mod_perl handlers and do something with it, apache doesn't work that
> way. Apache 2.0 does, but that won't help you right now. You might try
> using a proxy server setup to do this instead.
ah, yes. right, you can't intercept
> Assuming you mean you want to look at the generated content from
> non-mod_perl handlers and do something with it, apache doesn't work that
> way. Apache 2.0 does, but that won't help you right now. You might try
> using a proxy server setup to do this instead.
T
Andy Lester wrote:
> I want my MyFilter to process EVERYTHING that Apache spits out, whether
> with mod_perl, mod_php or just reading a .html file from the filesystem,
> especially the mod_php stuff.
Assuming you mean you want to look at the generated content from
non-mod_perl handle
Andy Lester wrote:
>
> > ok, SetHandler sets a content handler for a given - it supersededs
>everything else.
> >
> > unlike with normal Apache, mod_perl needs two things in order for your handler to
>be called:
> > the content hander to be perl-script (for Apache) and the name of your handler
> ok, SetHandler sets a content handler for a given - it supersededs
>everything else.
>
> unlike with normal Apache, mod_perl needs two things in order for your handler to be
>called:
> the content hander to be perl-script (for Apache) and the name of your handler with
>PerlHandler (for
> mod
Andy Lester wrote:
>
> How can I get mod_perl to handle all Apache output, whether or not it
> originates with mod_perl?
>
> I'm writing a module that needs to analyze all output generated by Apache.
> That's easy enough with stacked handlers, but I'm goofing
How can I get mod_perl to handle all Apache output, whether or not it
originates with mod_perl?
I'm writing a module that needs to analyze all output generated by Apache.
That's easy enough with stacked handlers, but I'm goofing something up
with, say, static HTML
into the problem is how I discovered the cleanup handler wasn't doing its
> > job in time.
>
> Want to see something even more interesting? Let your
> debugging warnings mention the pid that caused the log
> entry and let it run a while on a production server. I see
> stuff
On Feb 21, 2002 at 15:23:04 -0800, Milo Hyson wrote:
>
> On Wednesday 20 February 2002 07:55 pm, Geoffrey Young wrote:
> > >
> > > If the redirected request needs that session
> > > data, there's a small chance it won't be there yet.
> >
> > have you seen this? I don't recall this ever coming up
>
> I moved the session cleanup phase to a PerlLogHandler and it seems to be
> working, except for one small issue. Request URIs for directories (i.e. no
> filename specified) don't seem to trigger the log handler. I put some
> warnings in the code to trace its execution. The following is a d
On Wednesday 20 February 2002 07:55 pm, Geoffrey Young wrote:
> > If the redirected request needs that session
> > data, there's a small chance it won't be there yet.
>
> have you seen this? I don't recall this ever coming up before (which
> doesn't mean it can't happen :)
Yes, I have seen it ha
> My question was really about the proper way to call method handlers from
> either push_handlers or set_handlers since the normal technique (first
> example above) calls them as normal subs, i.e. the first parameter is not
> the class name. The second example, however, seems to do
> $r->push_handlers( PerlHandler => sub { Apache::Test->handler } );
>
> See
>
> http://perl.apache.org/guide/config.html#Perl_Method_Handlers, the eagle
> and cookbook books.
>
> PERL_METHOD_HANDLERS=1 + $$ prototype for Apache::Test::handler
My question was r
Milo Hyson wrote:
> I just ran into a problem with my PerlFixupHandler/PerlCleanupHandler based
> session manager (discussed earlier). It seems there's no guarantee that the
> cleanup handler will fire before the browser receives the response from the
> content handler.
um, yes there is.
1 - 100 of 280 matches
Mail list logo
