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
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 possibilities
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
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.
Hello,
GYmod_perl allows you to let your content handlers to focus on content -
GYall other parts of your application (authentication, session management,
GYproxying, URL rewriting tricks, etc) can programmed at the server level
GYvia other parts of the request cycle.
I think the question isn't
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,
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 a
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, an
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:
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 believe
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 the
* 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 says
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 time there are no params. It's as if calling
$apr-param strips them
or check out Apache::RequestNotes/
you'll also want to check out using Apache::Request-instance() over
Apache::Request-new()
HTH
--Geoff
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.
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 1.27_01-dev
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 installed.
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
.
--Anonymous
PGP Key 0xE0FA561B - Fingerprint:
7E18 C018 D623 A57B 7F37 D902 8C84 7675 E0FA 561B
- Original Message -
From: Joe Schaefer [EMAIL PROTECTED]
To: Issac Goldstand [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Monday, October 08, 2001 19:16
Subject: Re: Apache::Request
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 passed
princepawn == princepawn [EMAIL PROTECTED] writes:
princepawn Could someone point me to the documentation for
princepawn apache-based cookie handling?
perldoc Apache::Cookie
Jon
[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.
- 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 don't
Hello,
RHI get the following error on
RHmy $i = Apache::Request-instance($r);
RH
RHCan'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 reporting.
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 never
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 the method not
-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($r);
Can't locate object method instance via
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
-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.
- --
"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=something
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 $self =
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,
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=value1param2=0param3=value3. It appears that the 0 is being
interpretted as an empty string. Is this a bug/expected
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=value1param2=0param3=value3. It appears that the 0 is being
interpretted as an empty
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 case
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 check
for
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 check
for
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 :-)
--
Matt/
** Director and CTO **
** AxKit.com Ltd ** ** XML Application Serving **
**
-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, Dana C. Chandler III wrote:
Yes
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');
-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]
You're right... I was remembering
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;
Now send a request with the
-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]
ok, I see that. Apache
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
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:
_
warn
-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 problem occurs
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 and
-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't have
Apache::Request or
Apache::Cookie
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.
sounds to
]
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' load. Perl returns the no 'new' method could
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
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 works
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
from
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:
...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.
However
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,
in
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
Apache::Request eats up memory during a file upload
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
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 input type=image fields
in a multipart/form-data form.)
Jim
On
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: Please,
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 them, but
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 descriptors, the
tions 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: modperl [EMAIL PROTECTED]
Subject: Re: Apache::Request
On Tue, 11 Apr 2000, John S. Evans 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 them, but this requires a root access unless
you want to
t;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 currently using
Apache::Request to parse the POST that is used to upload a bunch of
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 diagnosing.
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 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'm
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
(which
72 matches
Mail list logo
