I have problems with Apache::SharedMem 0.07 installation.
Here is my configuration:
bash$ uname -a
Linux dallas 2.2.14-5.0 #1 Tue Mar 7 21:07:39 EST 2000 i686 unknown
bash$ perl -v
This is perl, v5.6.1 built for i686-linux
And here is 'make test' report:
bash$ make test TEST_VERBOSE=1
Alex Harper wrote:
>
> I'm using a mod_perl 1.26 RPM I built using the RedHat RPM prep files
> and dropping in the 1.26 code. I believe it is built EVERYTHING=1.
>
> Apache::Status indicates all hooks are enabled, including:
> PerlStackedHandlers Enabled
Okay. Would you mind putting some d
Hi!
I am wondering for installation of Apache weblogic?
Could you please tell me what is the exact address for Apache web logic? What is the installation process in Windows machine?
Your kind cooperation would highly appeciated
Thanks
Azimul
SydneyGet your FREE download of MSN Explorer at http:
I'm attempting to run some code off a
mounted drive on RH Linux 7.1 (Apache 1.3.2, modperl-1.26), but for some reason,
my Location directive is ignored (code is executed from the local drive
instead)
I'm pointing to /mnt/qa_load_www/cgi-shl,
but code is instead executed from /apache/cgi-sh
First off, if you could cc responses to me, that would be great.
On to the problem. I compiled apache 1.3.20 from sources, w/ the
following compiled statically:mm 1.1.3, mod_layout 3.0, mod_perl 1.25,
mod_ssl 2.8.4, and php 4.0.6. I am running perl 5.6.1, originally
installed from RPM and then up
Hi,
i'd like to write some analysis program using mod_perl which will
analyse the contents of pages which are sent to client.
the site is dynamic -- it uses SSI and CGI, and i would like to "hook"
into the phase when apache sends the pages after all processing (like
SSI) is done, and analyse the
On Fri, 28 Sep 2001 16:40, Steven Boger wrote:
> I've been netsearching for hours. It's time to beg for help...
>
> My apache has a hacked mod_include that has a new directive, OAS:
>
>
>
>
>
> Can I somehow run those directives right from mod_perl
If you have the Eagle book (if you don
On Fri, 28 Sep 2001 07:36, George Sanderson wrote:
> Apache::OpenIndex (OpenIndex-1.00.tar.gz) was uploaded to CPAN on 14Sep2001
> and is currently released. This was my first module. I enjoyed journey.
Looks really good. I think the mod_perl community can use a lot more
applications like thi
At 03:02 PM 9/27/2001 -0700, you wrote:
>George Sanderson wrote:
>>
>> Apache::OpenIndex (OpenIndex-1.00.tar.gz) was uploaded to CPAN on 14Sep2001
>> and is currently released. This was my first module. I enjoyed journey.
>>
>> OpenIndex provides a file manager for an Apache modperl web site u
I'm using a mod_perl 1.26 RPM I built using the RedHat RPM prep files
and dropping in the 1.26 code. I believe it is built EVERYTHING=1.
Apache::Status indicates all hooks are enabled, including:
PerlStackedHandlers Enabled
Alex
> --
> From: Daniel
> Sent: Monday, Oc
Did you compile mod_perl with PERL_STACKED_HANDLERS?
Perrin Harkins wrote:
> Alex Harper wrote:
>
>>Aha! That's where the problem lies. I had recently added:
>>PerlCleanupHandler +Apache::Sizelimit
>>
>>to my httpd.conf. I placed it there so the sizelimit would be enforced
>>post-reques
>-Original Message-
>From: Perrin Harkins
>To: Alex Harper
>Cc: Daniel; [EMAIL PROTECTED]
>Sent: 10/1/01 11:35 PM
>Subject: Re: CGI.pm params not being cleared?
>
>Alex Harper wrote:
>>
>> Aha! That's where the problem lies. I had recently added:
>> PerlCleanupHandler +Apache::
Alex Harper wrote:
>
> Aha! That's where the problem lies. I had recently added:
> PerlCleanupHandler +Apache::Sizelimit
>
> to my httpd.conf. I placed it there so the sizelimit would be enforced
> post-request. Removing the line fixed my problem.
Whoa! This could be bad. Apache::Size
Aha! That's where the problem lies. I had recently added:
PerlCleanupHandler +Apache::Sizelimit
to my httpd.conf. I placed it there so the sizelimit would be enforced
post-request. Removing the line fixed my problem.
This leads me to some questions:
1. If I declare handler modules in my
Odd, checking into my version CGI.pm (which I dont use), it cleans up
it's own globals by installing a cleanup handler:
Apache->request->register_cleanup(\&CGI::_reset_globals);
so either your version of CGI.pm is broken or your mod_perl was somehow
compiled without PERL_CLEANUP.
Alex Harper w
Thanks, I looked and we're not. Here's the simplest case:
use CGI;
my $cgi = new CGI;
my @params = $cgi->Vars();
print $cgi->header(-type => 'text/html');
print $cgi->start_html();
print "Process: $$\n";
print "Query String:\n";
print $ENV{QUERY_STRING} . "\n";
print "Params:\n";
pri
Make sure you're not doing:
use CGI;
my $cgi = new CGI;
if ($cgi->param("dataaction") eq "whatever") {
&do_whatever_without_passing_cgi();
}
elsif ($cgi->param("dataaction") eq "passcgi") {
&pass_it_cgi($cgi);
}
sub do_whatever_without_passing_cgi {
#using origi
I've just resolved a bug I was getting with parameter parsing, and was
told that I should pass it along to the mod_perl list (which I'd been
meaning to subscribe to anyway, so hey).
I'd been having problems getting CGI.pm to properly parse out script
parameters for various pages that had been wo
I actually forgot to mention that we had tried it with "my $cgi" and
$cgi. Neither worked.
As for switching to Apache::Request, no can do. We need to maintain
mod_cgi compatibility for at least a few more months.
Alex
--
Alex Harper
Configuration Management
[EMAIL PROTECTED]
"Use whatever you
On Mon, 1 Oct 2001, Alex Harper wrote:
> Date: Mon, 1 Oct 2001 16:16:34 -0500
> From: Alex Harper <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: CGI.pm params not being cleared?
>
> I'm sure this is a FAQ somewhere, but I'm not finding it...
>
> In our switch to mod_perl we're seeing two
I'm sure this is a FAQ somewhere, but I'm not finding it...
In our switch to mod_perl we're seeing two problems with CGI.pm (version
2.752). I'm uncertain if they are related or not.
1. Across multiple requests to a single script, the params are not
cleared. The first params sent to that script
I've got some availability at the moment so if anyone needs anything
from a couple of hours sorting out performance issues (and therefore
avoiding that costly upgrade!) up to planning and implementing major
rearchitectures, let me know. Check my site for recent projects,
references supplied from
> -Original Message-
> From: Bryan T. Schmidt [mailto:[EMAIL PROTECTED]]
> Sent: Monday, October 01, 2001 1:00 PM
> To: Bryan T. Schmidt
> Cc: [EMAIL PROTECTED]
> Subject: Re: generic symbol problems with LogFile
>
[snip]
>
> Bryan T. Schmidt wrote:
>
> This seems funny to me...
>
> -Original Message-
> From: Alin Simionoiu [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, September 30, 2001 7:04 PM
> To: Thomas Eibner
> Cc: Issac Goldstand; [EMAIL PROTECTED]
> Subject: Re: Keeping POST information between request phases
>
>
> I tried instance, but is not working is yo
On Sun, Sep 30, 2001 at 04:03:43PM -0700, Alin Simionoiu wrote:
> I tried instance, but is not working is you want to access let's say,
> POST data in a authentication handler, doing same data validation or
> whatever you want to do, and also access the same POST data at response
> phase.
>
> And
I tried instance, but is not working is you want to access let's say,
POST data in a authentication handler, doing same data validation or
whatever you want to do, and also access the same POST data at response
phase.
And this is because, as it is explained in guide, POST data are
retrieved direc
On Sun, Sep 30, 2001 at 03:23:51PM -0700, Alin Simionoiu wrote:
> Apache::Request->instance($r) will not work for POST reqests.
> At list will not do what you want.
Apache::Request->instance works very well with POST requests.
From the documentation:
instance
The instance() class method al
Apache::Request->instance($r) will not work for POST reqests.
At list will not do what you want.
Read this for more information:
http://perl.apache.org/guide/snippets.html#Reusing_Data_from_POST_request
On Sun, 2001-09-30 at 09:15, Thomas Eibner wrote:
> On Sun, Sep 30, 2001 at 05:59:08PM +020
Oops... was trying to send to the dev list and accidentally sent to this
one again.
Sorry.
-Bryan
Please read the following posts I made to the mod_perl users list (
[EMAIL PROTECTED] ) ... Someone there suggested that the dev list
might be able to help me better.
Is it appropriate to email the module author directly on something
like this?
Thanks in advance!
-Bryan
--
Bryan T
Gerald Richter <[EMAIL PROTECTED]> wrote:
>>
>> Wouldn't it be better to subclass Apache::SSI instead of
>> HTML::Embperl::Syntax::SSI ? That part of it would be really easy - the
>> hard part would be actually implementing the OAS directive actions.
>>
>>
>
> If you really only want to do SSI,
>
> Wouldn't it be better to subclass Apache::SSI instead of
> HTML::Embperl::Syntax::SSI ? That part of it would be really easy - the
> hard part would be actually implementing the OAS directive actions.
>
>
If you really only want to do SSI, then subclassing Apache::SSI is of course
the easier
> I am occasionally getting the following message from CGI.pm in $@:
>
> Line 1: Setup of CGI.pm failed:
>
That error message comes from Embperl. Embperl setup CGI.pm to get a file
upload. When something went wrong with this file upload, CGI.pm dies, which
is catched with this line:
>
> eval { $c
On Friday, September 28, 2001, at 08:49 AM, Nick Tonkin wrote:
> On Fri, 28 Sep 2001, Ask Bjoern Hansen wrote:
>
>> On Thu, 20 Sep 2001, Mike Schienle wrote:
>>
thanks to patches from Brice D. Ruth and others, a new version of
MSIISProbes.pm is available at
http://www.tonkinresolu
Hi, I have just come across this thread and have the exact same problem
(http://aspn.activestate.com/ASPN/Mail/Message/modperl/677372)
I am trying to build perl 5.6.0, DBD-Oracle-1.12 with DSO Apache 1.3.20 and
mod_perl-1.26 on Solaris 7 (uname -r = 5.7?)
Everything builds fine, however when
I have a TransHandler which does quite a few things - which under
certain circumstance calls a function defined in another package. Now
that function is supposed to do a internal redirect. What I am currently
observing is that the internal redirect takes place perfectly but the
the Handler then go
36 matches
Mail list logo
