Hey everyone,
I am having a tough time to parse the "query_string".
Does anyone know where I can find man page about
how the Apache construct the "query_string"?
Additionlly, is it right that Apache will place
the returned "query_string" in "STDIN".
Thanks! MIke
___
Yeah, I have the tendancy of sliding in and out of backslashism from
time to time. I often do it to impress the kids ;) Kidding aside, I
agree, it does makes things more easier to read though.
-Carlos
Stas Bekman wrote:
Carlos Ramirez wrote:
Here's the latest 'diff -u' ;) (Thanks for the tip
Carlos Ramirez wrote:
Here's the latest 'diff -u' ;) (Thanks for the tip Stas)
If you don't mind, Carlos, a few readability tips to give less reason for
people to state that perl is a write-once language.
Avoiding backslashism makes your code much more readable:
+## Parse $name's with Domai
Here's the latest 'diff -u' ;) (Thanks for the tip Stas)
Diff includes:
* Fixes in authz() as suggested by Jason Lehman.
* Apache::Htgroup is optional. I'm eval'in 'require Apache::Htgroup' as
shown in the links provided by Eric.
Full source:
http://www.quantumfx.com/software/modules/Apache-Au
William McKee wrote:
On Tue, Mar 23, 2004 at 02:14:44PM -0600, Brian Clarkson wrote:
I might need to take a look at that patch. The error that shows up is
from sub authen_ses_key
My patch is attached. I'm not sure it will help much if you're having
problems reading in the key but let me
On Tue, Mar 23, 2004 at 12:24:13PM -0600, Brian Clarkson wrote:
> Permissions look OK:
>
> [hostname ] $ ls -al keyfile
> -rw---1 nobody nobody 52 Mar 1 11:22 keyfile
Out of curiosity, have you tried setting the permissions on that keyfile
to 666 to be sure that another pro
On Tue, Mar 23, 2004 at 02:14:44PM -0600, Brian Clarkson wrote:
> I might need to take a look at that patch. The error that shows up is
> from sub authen_ses_key
My patch is attached. I'm not sure it will help much if you're having
problems reading in the key but let me know how it goes.
Nick Phillips wrote:
On 24/03/2004, at 6:24 AM, Brian Clarkson wrote:
The host in question is a VirtualHost. My first configuration
attempt, which matches one of the more common solutions ( putting the
PerlSetVar directive before the module load ) doesn't do the trick:
You *must* put *all*
On 24/03/2004, at 6:24 AM, Brian Clarkson wrote:
The WhateverDBI_SecretKeyFile seems to be everyone's problem with this
module. I've searched around, read most people's fixes, but none of
them work for me. Here's my error_log snippet:
[Tue Mar 23 12:04:58 2004] [error] access to /LOGIN failed
On Tuesday 23 March 2004 10:14 am, Stas Bekman wrote:
> Thanks for the report, Beau. I'm looking at it. I'm going to rewrite the
> code not to load Apache::Request till we know that we have found the right
> version.
OK. Send a patch if you want a pre-test on my platform.
Aloha => Beau;
--
Rep
William McKee wrote:
Hi Brian,
I've had my share of problems with this module as well. I've found the
following two solutions which I submitted to CPAN RT[1]:
1) place the PerlSetVar at the very top of your httpd.conf
In the Global ENV section? Doesn't fix the issue.
2) instead of using
Thanks for the report, Beau. I'm looking at it. I'm going to rewrite the code
not to load Apache::Request till we know that we have found the right version.
__
Stas BekmanJAm_pH --> Just Another mod_perl Hacker
http:/
Hi Brian,
I've had my share of problems with this module as well. I've found the
following two solutions which I submitted to CPAN RT[1]:
1) place the PerlSetVar at the very top of your httpd.conf
2) instead of using PerlModule, use the following:
use Apache::AuthCookie
On Tue, 2004-03-23 at 10:52, Chris Gamache wrote:
> I wrote a load-testing script that hits my Apache webapp with 100 serialized
> requests. The webapp works great that way. If I start multiple simultaneous
> instances of the load-testing script, the requests eventually fail.
Anything will fail i
The WhateverDBI_SecretKeyFile seems to be everyone's problem with this
module. I've searched around, read most people's fixes, but none of
them work for me. Here's my error_log snippet:
[Tue Mar 23 12:04:58 2004] [error] access to /LOGIN failed, reason:
Apache::AuthCookieDBI: didn't have the
Geoffrey Young wrote:
Michael Taylor wrote:
I am having problems trying to migrate some Perl code (that I didn't write) from
mod_perl 1 (and libapreq 1) to mod_perl 2 (and libapreq2).
I don't understand why I having problems with this simple code example.
$apr->notes( 'mm_secure' => 0 );
Hi there,
Hello there,
> first time posting on this list.
Welcome!
On Tue, 23 Mar 2004, Chris Gamache wrote:
> I'm not sure what information you'd need
When your message was returned to you from the mod_perl List you will
see that there was added:
> Report problems: http://perl.apache.org/bu
On Tue, 23 Mar 2004 11:47:01 -0500, Jamie LeTual wrote:
> This won't help if the database is running on a different machine. If
> the apache and mysql are on the same machine, this will work although
> there are security concerns regarding this.
Good points. I can live with the limitations for
Hi,
> Well, I tried increasing the max packet size, but all that did was decrease
> the frequency of the problem appearing. I increased it from 1MB to 8MB.
> Think that was enough?
You never send us a code fragment did you? The thing puzzling me is
"decrease the frequency"... I agree with Andrew
Michael Taylor wrote:
> I am having problems trying to migrate some Perl code (that I didn't write) from
> mod_perl 1 (and libapreq 1) to mod_perl 2 (and libapreq2).
>
> I don't understand why I having problems with this simple code example.
> $apr->notes( 'mm_secure' => 0 );
looks lik
Andrew Green wrote:
Frankly, if you're not sure of an upper limit to the size of data you
might need to try to write to the database, sooner or later you're bound
to have to try to send something too big. I'd really suggest looking
into the Storable or FreezeThaw CPAN modules as a way of just dum
I am having problems trying to migrate some Perl code (that I didn't write) from
mod_perl 1 (and libapreq 1) to mod_perl 2 (and libapreq2).
I don't understand why I having problems with this simple code example.
package Example;
use strict;
use mod_perl;
use Apache2;
use Apache::RequestRec;
us
I wrote a load-testing script that hits my Apache webapp with 100 serialized
requests. The webapp works great that way. If I start multiple simultaneous
instances of the load-testing script, the requests eventually fail.
This is my first time posting on this list. I'm not sure what information yo
On Tue, 23 Mar 2004 10:25:12 -0500, Chris Miller wrote:
> Well, I tried increasing the max packet size, but all that did was
> decrease the frequency of the problem appearing.
I guess that's a pretty good indication that it was the packet size
problem biting you!
Frankly, if you're not sure of a
Well, I tried increasing the max packet size, but all that did was decrease
the frequency of the problem appearing. I increased it from 1MB to 8MB.
Think that was enough?
By the way, I think the code is using Apache::DBD. I'm a sys admin, not a
very good perl programmer. ;)
Still, I can restart a
On Tuesday 23 March 2004 01:27 am, Beau E. Cox wrote:
> On Tuesday 23 March 2004 12:55 am, Beau E. Cox wrote:
> > On Tuesday 23 March 2004 12:04 am, Beau E. Cox wrote:
> > > -8<-- Start Bug Report 8<--
> > > 1. Problem Description:
> > >
> > > Using latest
On Tuesday 23 March 2004 12:55 am, Beau E. Cox wrote:
> On Tuesday 23 March 2004 12:04 am, Beau E. Cox wrote:
> > -8<-- Start Bug Report 8<--
> > 1. Problem Description:
> >
> > Using latest (CVS) Apache2, mod_perl 2, libapreq2:
> >
> > t/modules/apache_s
On Tuesday 23 March 2004 12:04 am, Beau E. Cox wrote:
> -8<-- Start Bug Report 8<--
> 1. Problem Description:
>
> Using latest (CVS) Apache2, mod_perl 2, libapreq2:
>
> t/modules/apache_status fails
>
> console log:
>
> [...]
>
> error_log:
>
> [...]
-8<-- Start Bug Report 8<--
1. Problem Description:
Using latest (CVS) Apache2, mod_perl 2, libapreq2:
t/modules/apache_status fails
console log:
server localhost:8550 listening (TestDirective::perlloadmodule6)
t/modules/apache_status1..11
# Run
29 matches
Mail list logo
