RE: help on setting up a PerlFixupHandler

2003-08-06 Thread csebe
Hi, It seems to me that $r->content-type is for what your server sends to the client, which is probably undef in the Fixup stage, where you test it. You probaly meant to test for the $ct = $r->header_in("Content-type") if you wanted to see whats requested from the client. Anyway, as Christopher

Re: help on setting up a PerlFixupHandler

2003-08-06 Thread Xavier Noria
[EMAIL PROTECTED] wrote: It seems to me that $r->content-type is for what your server sends to the client, which is probably undef in the Fixup stage, where you test it. You probaly meant to test for the $ct = $r->header_in("Content-type") if you wanted to see whats requested from the client. But

RE: HTTP POST: parameters "empty" when using ModPerl::Registry(okay when using ModPerl:PerlRun)...

2003-08-06 Thread Perrin Harkins
On Wed, 2003-08-06 at 04:50, Steve Bannerman wrote: > However, it doesn't really explain why the "root problem" exists. The way I > think about it, the creation of a new CGI "object" should create a new "set > of slots" for instance data. That would make sense, but very little about CGI.pm actual

ModPerl - CGI in the same request phase

2003-08-06 Thread csebe
Hi again everybody, I have the following interesting (I hope ;-) requirement. Sorry for this rather long posting. (mod_perl 1, Apache 1.3.27) I have a custom authentication & authorization handler of mine which is the king in a protected directory (and its subdirectories): PerlModule MyModules::

RE: HTTP POST: parameters "empty" when using ModPerl::Registry (okay when using ModPerl:PerlRun)...

2003-08-06 Thread Steve Bannerman
Christopher, Thanks for the suggestion; unfortunately, it doesn't work. I made the change you suggested (inserting "CGI->initialize_globals();" just before creating an instance of CGI) and restarted apache/httpd. The same result...the first time the script executes it saves the file properly...a

Re: help on setting up a PerlFixupHandler

2003-08-06 Thread Xavier Noria
On Wednesday 06 August 2003 18:29, Geoffrey Young wrote: > > sub handler { > > my $r = shift; > > > > return DECLINED if $r->content_type ne 'text/html'; > > return SERVER_ERROR unless $r->can_stack_handlers; > > > > $r->set_handlers(PerlHandler => ['ContentHand

Re: Re[2]: Multiple select

2003-08-06 Thread Perrin Harkins
On Tue, 2003-08-05 at 13:29, Alan Rafagudinov wrote: > Please small example of using Apache::Request. > > $r->content; > $r = Apache->request; > > does not work :-( That's not Apache::Request, that's an Apache object. Please read the documentation: http://perl.apache.org/docs/1.0/guide/porti

the installation nightmare continues

2003-08-06 Thread Hodge, Jeff F (ECIII)
Title: the installation nightmare continues Taking a step or two back I have started the process over again.  I have created my download directory for a non-root user and built and compiled perl 5.8.0, which went smoothly and passed all of the tests along the way.  This brings me to mod_perl

Re: [mp2] Child process exited

2003-08-06 Thread Jean-Sebastien Guay
> 25k zip? that's a not quite a short test case ;) Can it possibly be 25 lines > of code instead? You're absolutely right, I've pared it down a lot while waiting for your answer. I was trying to get my test case to you as fast as possible, that's why I didn't spend that much time on it before. It'

Re: Trouble with Apache::Request

2003-08-06 Thread Randy Kobes
On Fri, 1 Aug 2003, Jie Gao wrote: > Hi All, > > perl-5.8.0 + mp1.99_10. > --- > > I am having problem trying to get /perl-status work. > > It bombs out in Status.pm at the following location: > > -- > if (

Re: the installation nightmare continues

2003-08-06 Thread Geoffrey Young
So I built, tested and made apache with: $ ./configure --prefix=/usr/local/apache $ make $ make install $ usr/locall/apache/bin/apachectl start (started fine) try letting mod_perl do the heavy lifting - mod_perl will build both itself and apache if you let it. after unzipping both apache and m

RE: HTTP POST: parameters "empty" when using ModPerl::Registry (okay when using ModPerl:PerlRun)...

2003-08-06 Thread Christopher Knight
try CGI->initialize_globals(); at the begining of the script but before you use params if you are depending on the 'use CGI' statement to initialize your params (like a command line script), it will cause problems in Registry. Thats becuase it is initialized once on the initial 'use CGI' and it