On Wed, 2003-07-02 at 20:38, Andrew Ho wrote:
> I totally agree with the fact that Apache::Registry can introduce many
> hard-to-debug-problems. I've had enough headaches debugging some of these
> issues myself. It's unclear to me, though, that there are unimaginably
> cool things you can get to in
It's unclear to me, though, that there are unimaginably
cool things you can get to in a "real" content handler that you can't get
to from an Apache::Registry script--which seems to be the assertion.
well, if you consider that you still get access to $r and all its treasures
from Apache::Registry,
Hello,
GY>mod_perl allows you to let your content handlers to focus on content -
GY>all other parts of your application (authentication, session management,
GY>proxying, URL rewriting tricks, etc) can programmed at the server level
GY>via other parts of the request cycle.
I think the question isn
Jesse Erlbaum wrote:
Philippe --
Check out the guide:
Check out the books:
Check out the success stories:
Is that your answer? I was hoping for specific examples, not
hand-waving.
I like to think that Part III (Chapters 11-17) of the mod_perl Developer's
Cookbook does some of that.
authent
Philippe --
> Check out the guide:
> Check out the books:
> Check out the success stories:
Is that your answer? I was hoping for specific examples, not
hand-waving.
-Jesse-
--
Jesse Erlbaum
The Erlbaum Group
[EMAIL PROTECTED]
Phone: 212-684-6161
Fax: 212-684-6226
On Wed, 2003-07-02 at 22:36, Jesse Erlbaum wrote:
> Hi Joe --
>
> > +1. Scripting _inside_ the server opens up possibilities that
> > are unimaginable to folks who are content confining themselves
> > to the lowest common denominator (CGI).
>
> Perhaps you could bullet-point a few of these poss
Hi Joe --
> +1. Scripting _inside_ the server opens up possibilities that
> are unimaginable to folks who are content confining themselves
> to the lowest common denominator (CGI).
Perhaps you could bullet-point a few of these possibilities for those of
us who are confined by our lack of imagin
"Hector Pizarro" <[EMAIL PROTECTED]> writes:
[...]
> If the user closes the popup in the middle of an upload, Apache::Request
> parse() isn't throwing any error, and all the following code in my module
> savesthe file incomplete in the system, which of course is garbage data.
>
> Is this a bug,
Ewald Geschwinde wrote:
I have read that the param Method had been deprecated
$r->param('value'):
How do I get now the variables from a submitted form ??
now? when? nothing has changed with Apache::Request. No April Fools jokes here.
__
Andrew Alakozow wrote:
Hello,
I use Apache::FakeRequest to test perl handlers without firing up Apache.
Testting is supposed to be done by matching output of handlers with some
regexps. But the print method of Apache::Request prints to STDOUT, so to
get output I applied following patch to it:
10c
dorian wrote:
> aiya. libapreq 0.31 is the one that likes to append whatever it is
that one just uploaded
> to it to its heap until it starves your machine of memory, if i recall
correctly. it was
> fixed in 0.31_03 i believe but it looks like 1.1 was released last
week.
I have found 1.1 on CP
> I downloaded Apache::Request from CPAN and I have version 0.31. My C
> compiler is gcc 2.96
aiya. libapreq 0.31 is the one that likes to append whatever it is that
one just uploaded to it to its heap until it starves your machine of memory,
if i recall correctly. it was fixed in 0.31_03 i believ
Hello,
We use this patch (on Apache::Filter 1.019) and it works ok. It won't
get you up and running with Apache::Registry, but it will do if you can
initialize the filter yourself.
Add this to Filter.pm:
sub Apache::Request::filter_register {
my $r= shift;
@ISA = qw(Apache::Request);
On Mon, 26 Aug 2002, Ufuk Yuzereroglu wrote:
> I dont know if this is the right place to ask but I just cant
> install Apache::Request. When calling 'make', make cant find
> any of the header files. Can anyone tell me where I did go
> wrong?
Did you install mod_perl and apache successfully on th
> > or check out Apache::RequestNotes/
>
>
> you'll also want to check out using Apache::Request->instance() over
> Apache::Request->new()
That is indeed the three second code fix that I implemented.
> or check out Apache::RequestNotes/
you'll also want to check out using Apache::Request->instance() over
Apache::Request->new()
HTH
--Geoff
TED]]
> Sent: 05 July 2002 15:57
> To: modperl
> Subject: Re: Apache::Request $apr->param; problems.
>
>
> * Wes Cravens <[EMAIL PROTECTED]> [2002-07-05 10:48]:
> > however if this routine is called more than once with the same $r
> > object then the second
* Wes Cravens <[EMAIL PROTECTED]> [2002-07-05 10:48]:
> however if this routine is called more than once with the same $r
> object then the second time there are no params. It's as if calling
> $apr->param strips them off $r. That's not clever. I can't find
> anything in the documentation that
That worked!!
I had installed the ActiveState libapreq.
Thanks for your help on this!
> On Sun, 23 Jun 2002, Levon Rubin Barker wrote:
>
>> Hello.
>>
>> I'm sure this is a simple problem, but I'm a noob at mod_perl and
>> could use some help.
>>
>> I am running WinXP, Apache 1.3.26, Mod_perl
On Sun, 23 Jun 2002, Levon Rubin Barker wrote:
> Hello.
>
> I'm sure this is a simple problem, but I'm a noob at mod_perl and could use
> some help.
>
> I am running WinXP, Apache 1.3.26, Mod_perl 1.27_01-dev with libapreq 0.31/
>
> The problem I am having is ...
>
> I get the following in the Ap
On Sun, 23 Jun 2002, Levon Rubin Barker wrote:
> Hello.
>
> I'm sure this is a simple problem, but I'm a noob at mod_perl and could use
> some help.
>
> I am running WinXP, Apache 1.3.26, Mod_perl 1.27_01-dev with libapreq 0.31/
There's a libapreq-1 out now, in $CPAN/authors/id/J/JI/JIMW/ ...
On Fri, 4 Jan 2002, Dan Horne wrote:
> I've been trting to get mod_perl working under cygwin. I've manages to
> install both Apache and mod_perl and have tested the earlier scripts in the
> O'Reilly "Writing Apache Modules" -e.g. The guestbook app.
>
> However, I can't get Apache::Request install
John Michael wrote:
I have a modperl script that uses.
cgi.pm and actually I have been importing my on cgi params from get and
post but do use cgi.pm for cookies. I have read in some other emails
and now in the guide that it is faster to use Apache::Request so I want
to change my script over t
Issac Goldstand" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, October 08, 2001 19:16
Subject: Re: Apache::Request UPLOAD_HOOK
> "Issac Goldstand" <[EMAIL PROTECTED]> writes:
>
> > The documentation on how to use this feature is a bit sketchy
"Issac Goldstand" <[EMAIL PROTECTED]> writes:
> The documentation on how to use this feature is a bit sketchy...
Yes, I agree. Doc patches are always welcome.
Comments below are from memory since I last tested this feature
about 6 months ago.
> Can anyone explain: 1) What the variables pas
> "princepawn" == princepawn <[EMAIL PROTECTED]> writes:
princepawn> Could someone point me to the documentation for
princepawn> apache-based cookie handling?
perldoc Apache::Cookie
Jon
- Original Message -
From: "princepawn" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, September 01, 2001 4:52 PM
Subject: Apache::Request cookie handling methods?
> p.209 of the Eagle Book states that Apache::Request has some
> experimental cookie-handling functions.
I d
[EMAIL PROTECTED] (princepawn) wrote:
>p.209 of the Eagle Book states that Apache::Request has some
>experimental cookie-handling functions. However, neither perldoc
>Apache or perldoc Apache::Request has the word cookie anywhere in
>their body.
The cookie-handling stuff is called Apache::Cookie.
Hello,
RH>I get the following error on
RH>my $i = Apache::Request->instance($r);
RH>
RH>Can't locate object method "instance" via package "Apache::Request"
Just to avoid the "whoops" factor: make sure you have "use Apache::Request"
in your script, too. This can also cause the error you are repor
>-Original Message-
>From: Robin Berjon
>To: [EMAIL PROTECTED]
>Sent: 8/15/01 4:39 PM
>Subject: Re: Apache::Request
>
>On Wednesday 15 August 2001 22:11, Rasoul Hajikhani wrote:
>> I get the following error on
>> my $i = Apache::Request->instance($
I am reading the online docs...
-r
Robin Berjon wrote:
>
> On Wednesday 15 August 2001 22:11, Rasoul Hajikhani wrote:
> > I get the following error on
> > my $i = Apache::Request->instance($r);
> >
> > Can't locate object method "instance" via package "Apache::Request"
> >
> > Why is that? Is th
On Wednesday 15 August 2001 22:11, Rasoul Hajikhani wrote:
> I get the following error on
> my $i = Apache::Request->instance($r);
>
> Can't locate object method "instance" via package "Apache::Request"
>
> Why is that? Is the method not available? Are the docs outdated?
> Any comments welcomed...
At 1:11 PM -0700 8/15/01, Rasoul Hajikhani wrote:
>I get the following error on
>my $i = Apache::Request->instance($r);
I think you want
my $i = Apache::Request->new($r);
I've never used or seen instance before, but I've only been doing
mod_perl for about 20 months.
Rob
--
"A good magician n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At 1:07 AM +1000 4/7/01, Cees Hek wrote:
> $r->param('newlist' => [qw(one two three)]);
>
> my @newlist = $r->param('newlist');
my @newlist = @{$r->param('newlist')};
What you stored was not an array, but a reference to an array
this was fixed in cvs this past month. check out the archive of the
apreq-dev list (if there is one somewhere) to see the details. basically it
was because using param() to set a variable was calling Apache::Table->set,
which stringifies its arguments. Now it calls Apache::Table->add and does
On Mon, 12 Mar 2001, Gene Dascher wrote:
> How can I access the Apache Request object from a Perl package that I am
> calling from a Perl Authorization handler?
$r is the first argument passed to your handler.
my $r = shift;
> I tried using the following code in TestPackage.pm:
>
> my $r = Apa
> Pulling parameters from a POST method using Apache::Request,
> largely to make
> it easier to deal with multiple value variables. The problem
> occurs if I
> have two variables, differentiated only by case (eg.
> wanthelp=
> and wantHelp=).
>
> Am I missing some parameter to make this case
"James Sheridan-Peters" <[EMAIL PROTECTED]> writes:
> Quick summary:
>
> Pulling parameters from a POST method using Apache::Request, largely to make
> it easier to deal with multiple value variables. The problem occurs if I
> have two variables, differentiated only by case (eg. wanthelp=
> and
On Sat, 30 Dec 2000, Matt Sergeant wrote:
> > Another minor issue is that Apache::Request is not trivially subclassed,
> > the returned value from $self->SUPER::new() must be reblessed into the
> > desired class.
>
> Thats a pretty standard perl idiom:
>
> sub new {
> my $class = shift;
> my
On Sun, 24 Dec 2000, Shevek wrote:
> I want the parameters from the first request to be preserved into the
> subrequest.
Store in a global variable then:
$MyPackage::request = $apr;
Then access in the internal redirect.
> Another minor issue is that Apache::Request is not trivially subclassed
On Tue, 28 Nov 2000, Ryan Adams wrote:
>
> Excuse me if this is a ridiculous question, but is there any way
> to install Apache::Request on a Windows box without VC++?
[ ... ]
Hi,
No - it requires a C compiler ... Even with VC++, though,
some changes to the distribution are needed to get it
On Tue, Sep 26, 2000 at 01:06:33PM -0400, Geoffrey Young wrote:
> mod_perl wasn't built with EVERYTHING=1 (I'm not sure whether
> libapreq needs PERL_TABLE_API=1 or not)
In fact I needed to rebuild mod_perl with this enabled in order to have
Apache::Request works properly.
--
Ciao, Mauriz
> -Original Message-
> From: Matt Sergeant [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, October 05, 2000 10:53 AM
> To: Geoffrey Young
> Cc: Dana C. Chandler III; [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: RE: Apache::Request and parameters = 0
>
[snip]
On Thu, 5 Oct 2000, Geoffrey Young wrote:
> > package FooTest;
> > use Apache::Constants;
> > use Apache::Reload;
> >
> > sub handler {
> > my $r = shift;
> > $r->send_http_header;
> > print "Args: ", scalar $r->args, "\n";
> > return OK;
> > }
> >
> > 1;
> >
>
> -Original Message-
> From: Matt Sergeant [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, October 05, 2000 10:26 AM
> To: Geoffrey Young
> Cc: Dana C. Chandler III; [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: RE: Apache::Request and parameters = 0
[snip]
>
&g
On Thu, 5 Oct 2000, Geoffrey Young wrote:
> however, just for clarity, I don't see how this is a bug in Apache::Request
> (as you originally pointed out)...
>
> #!/usr/bin/perl
> use Apache::Request;
> my $r = Apache::Request->new(shift);
> my $value = $r->param('foo');
>
> $r->send_http_header
> -Original Message-
> From: Matt Sergeant [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, October 05, 2000 9:57 AM
> To: Dana C. Chandler III
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: Apache::Request and parameters = 0
>
>
> On Thu, 5 Oct 2000,
On Thu, 5 Oct 2000, Dana C. Chandler III wrote:
> Yes, in particular,
>
> $value = $r->param('name') || "";
Or worse, $r->param('name') || "3"; # default but true
Even I'm guilty of that one sometimes :-)
--
** Director and CTO **
** AxKit.com Ltd ** ** XML Application Serving **
** ht
Matt Sergeant wrote:
>
> On Thu, 5 Oct 2000, Dana C. Chandler III wrote:
>
> > In my limited experience, it is Perl in general that treats the value 0,
> > in a query string as the empty string. In all of the scripts I have
> > written, if 0 is possible as a param value, I have to explicity che
Matt Sergeant wrote:
>
> On Thu, 5 Oct 2000, Dana C. Chandler III wrote:
>
> > In my limited experience, it is Perl in general that treats the value 0,
> > in a query string as the empty string. In all of the scripts I have
> > written, if 0 is possible as a param value, I have to explicity che
On Thu, 5 Oct 2000, Dana C. Chandler III wrote:
> In my limited experience, it is Perl in general that treats the value 0,
> in a query string as the empty string. In all of the scripts I have
> written, if 0 is possible as a param value, I have to explicity check
> for 0.
This is only the ca
Matt Sergeant wrote:
>
> On Thu, 5 Oct 2000, John Reid wrote:
>
> > Hi guys
> >
> > Has anyone any experience of passing a 0 as a parameter value through
> > Apache::Request. I am passing a QUERY_STRING like
> > ?param1=value1¶m2=0¶m3=value3. It appears that the 0 is being
> > interpretted as an
On Thu, 5 Oct 2000, John Reid wrote:
> Hi guys
>
> Has anyone any experience of passing a 0 as a parameter value through
> Apache::Request. I am passing a QUERY_STRING like
> ?param1=value1¶m2=0¶m3=value3. It appears that the 0 is being
> interpretted as an empty string. Is this a bug/expected b
On Thu, 24 Aug 2000, Ken Williams wrote:
> Hi all,
>
> It looks like setting Apache->request($r) doesn't work as documented. I
> can't get it to install a subclass of Apache as the request object.
>
> Here's some code in a handler:
> _
>
On Tue, 26 Sep 2000, Herrington, Jack wrote:
> I'm using Mason in process with mod_perl. I have also tried using mod_perl
> handlers direct with Apache::Request with no success.
what do you see if you configure Apache::Status and open the url:
/perl-status?Apache::Request
?
also, any differen
ECTED]
Subject: Re: Apache::Request->new() problem
On Mon, 25 Sep 2000, Herrington, Jack wrote:
> I have the same problem as one of the previous reporters with
> Apache::Request->new(). The problem occurs whether I call it after a
'use'
> or after a 'PerlModule'
On Mon, 25 Sep 2000, Herrington, Jack wrote:
> I have the same problem as one of the previous reporters with
> Apache::Request->new(). The problem occurs whether I call it after a 'use'
> or after a 'PerlModule' load. Perl returns the no 'new' method could be
> found for Apache::Request.
sound
> -Original Message-
> From: Herrington, Jack [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, September 26, 2000 12:17 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Apache::Request->new() problem
>
>
> >well, if you don't have that, then you likely don
>well, if you don't have that, then you likely don't have Apache::Request or
>Apache::Cookie - they aren't part of the mod_perl distribution :)
>you need libapreq, which can be found under the Apache tree on CPAN
libapreq appears to come with Bundle::Apache, but I also downloaded it
seperately an
> -Original Message-
> From: Herrington, Jack [mailto:[EMAIL PROTECTED]]
> Sent: Monday, September 25, 2000 10:36 PM
> To: [EMAIL PROTECTED]
> Subject: Apache::Request->new() problem
>
>
> I have the same problem as one of the previous reporters with
> Apache::Request->new(). The prob
On Mon, 25 Sep 2000, Sophokles Zafeiris wrote:
> I' m trying to run the file_upload.pl. script, that can be found in the eg
> directory of the Apache::Request source file. I've installed the
> Apache::Request but I get the following server error :
> Can't locate object method "new" via package "
On Aug 28, Dave Thomas wrote:
> I applied the patch from the archives but the httpd child process is
> still
> growing by the size of the file. Is that normal, or is there an update
> to the patch that Jim Winstead placed out there
>
> The system that I am running on is:
> SunOS 5.6 on a sparc U
The template contains the ENCTYPE="multipart/form-data",
uses METHOD="POST", and the action is my handler.
I initialize the object with:
my $r = 'Apache'->request();
my $apr = 'Apache::Request'->new($r);
From within my local CGI class I get the Apache::Request class reference
fro
At 10:04 AM 7/14/00 -0600, Dave Thomas wrote:
>Hello,
>
>Question: Why does the Apache::Request object not return an Upload
>object when
>there was a file sent.
>
> Backgroud: I have pulled the sample script from the Apache::Request
>distribution and
>used that in my handler, this instance w
> Okay, I think I tracked this down to a one-byte buffer overflow.
> Try the attached patch to see if that fixes it (it fixes things
> in my testing).
>
Oops. Please ignore my last message. Your fix works just fine... I had
some code to automatically kill my process after it got an upload >1MB,
i
<...Problem with patch to fix memory blow-out with file uploads...>
> Okay, I think I tracked this down to a one-byte buffer overflow.
> Try the attached patch to see if that fixes it (it fixes things
> in my testing).
>
Thanks--certainly an improvement. I tried a 25k file, which worked fine.
How
Okay, I think I tracked this down to a one-byte buffer overflow.
Try the attached patch to see if that fixes it (it fixes things
in my testing).
Unfortunately, the overflow seemed to sneak through with no problems
on FreeBSD, and on Linux if you compile with -g.
Jim
On Jun 24, dorian wrote:
> b
breaks for me too. null byte issue maybe? i don't know. i can't write c. :)
.djt
> Attached is a patch to libapreq that addresses this problem.
> <...>
Thanks for this, Jim. Unfortunately, I'm having some problems with the
patch. When I try and upload a file greater than a couple of k, I get a
segfault in httpd. Could you possibly email me your current working
libapreq sourc
On Thu, 22 Jun 2000, Jim Winstead wrote:
> Attached is a patch to libapreq that addresses this problem.
Question for Doug,
Can we get libapreq 0.32 out any time soon? There are some pretty nasty
bugs in 0.31 that I'm waiting to get fixed. (the null cookies problem,
this problem, the form charse
Attached is a patch to libapreq that addresses this problem.
(Doug, this may be updated since we last sent you this patch to
resolve issues with IE 4.5 on the Mac, which doesn't terminate the
MIME boundary correctly when there are fields
in a multipart/form-data form.)
Jim
On Jun 21, dorian wr
At 02:04 PM 4/30/00 -0400, Sam Carleton wrote:
>Tobias,
>
>The new is blowing up on me. This is the error message:
>
>null: Can't locate object method "new" via package "Apache::Request"
Try installing it :-)
$ perl -MCPAN -e shell
cpan> install Apache::Request
Tobias
PS: Pl
On Thu, 20 Apr 2000, Doug MacEachern wrote:
> On Thu, 13 Apr 2000, Stas Bekman wrote:
>
> > > I have no real conclusion to reach, except that it seems to be leaking
> > > files.
> >
> > Well, I wanted to write Apache::FileLeak or an extension to
> > Apache::VMonitor to show the opened file desc
On Thu, 13 Apr 2000, Stas Bekman wrote:
> > I have no real conclusion to reach, except that it seems to be leaking
> > files.
>
> Well, I wanted to write Apache::FileLeak or an extension to
> Apache::VMonitor to show the opened file descriptors, the files and the
> processes that have opened the
> I have no real conclusion to reach, except that it seems to be leaking
> files.
Well, I wanted to write Apache::FileLeak or an extension to
Apache::VMonitor to show the opened file descriptors, the files and the
processes that have opened them, but this requires a root access unless
you want to
Thanks for the advice so far! If you have better instructions for using
lsof, I'd also appreciate that!
-jse
> From: Doug MacEachern <[EMAIL PROTECTED]>
> Date: Wed, 12 Apr 2000 22:48:06 -0700 (PDT)
> To: "John S. Evans" <[EMAIL PROTECTED]>
> Cc: mod
On Tue, 11 Apr 2000, John S. Evans wrote:
> I'm using Solaris (SunOS 5.7, according to uname).
>
> The number of files varies, and I can control this if I know what the limits
> are. Is the 256 limit per process or for the entire machine? For instance,
> if I have 10 apache children going full
On Tue, Apr 11, 2000 at 11:52:44PM -0700, John S. Evans wrote:
> I saw (in the code) that there's one open file per uploaded file. That
> should be fine. I just need to find out if they're getting closed
> correctly.
>
> What is "lsof"?
'LiSt Open Files', its really a handy tool for diagnos
00 21:26:19 -0700 (PDT)
> To: "John S. Evans" <[EMAIL PROTECTED]>
> Cc: modperl <[EMAIL PROTECTED]>
> Subject: Re: Apache::Request
>
> On Mon, 10 Apr 2000, John S. Evans wrote:
>
>> I'm looking for some help/advice with Apache::Request. I'm cu
On Mon, 10 Apr 2000, John S. Evans wrote:
> I'm looking for some help/advice with Apache::Request. I'm currently using
> Apache::Request to parse the POST that is used to upload a bunch of files to
> our server.
how many files? what os are you using? solaris has a 256 limit.
> The problem I
Ilya Obshadko wrote:
>
> Hello,
>
> I've discovered the following. Suggest that you use Apache::Request
> object in both fixup handler and registry script. So we have:
>
> 1) unpredictable segmentation faults
I had the same problem. I think there must be some problems in libapreq
(whic
81 matches
Mail list logo
