I think I have found a curious bug in DBI. It seems that since DBI 1.15
- 1.20, when you bring up apache/mod_perl and execute queries against
the database handle in the parent process (startup.pl), multiple
connections result against the database. If I switch to DBI 1.14, no
such problem
I was wondering if anyone is currently using perl 5.6 + mod_perl in a
prod environment.
What kinds of problems, if any are people seeing with this?
--eric
Yes, I have NLS_LANG set to AMERICAN_AMERICA.WE8ISO8859P1. BTW, I am
also using the latest oracle client libs (8.17) if this makes any
difference; as well, I am using perl 5.005.
--eric
Ged Haywood wrote:
Hi there,
On Mon, 11 Jun 2001, Eric Kolve wrote:
I recently upgraded to DBI 1.18
I found something a bit curious that I was wondering if someone could
explain. I have the following apache::registry script I called test.reg:
#!/usr/bin/perl
use strict;
if($test){
# do stuff
}
print qq|HTTP/1.1 200 OK\r\n|;
print HELLO WORLD\n\n;
I ran my server in single-user mode
I was wondering if someone could explain to me why in the eagle book it
is necessary to perform
an md5 twice before sending a mac_check to a user of a number of
fields. I read in the mod_perl book that this is done 'to prevent
technically savy users from appending data to the @fields'.
my
I was wondering if someone could explain to me why in the eagle book it
is necessary to perform
an md5 twice before sending a mac_check to a user of a number of
fields. I read in the mod_perl book that this is done 'to prevent
technically savy users from appending data to the @fields'.
my
I noticed in the modperl guide
(http://perl.apache.org/guide/scenario.html#Buffering_Feature), they
recommend setting rmem_max to a size such that you will buffer all pages
sent from modperl to a proxy in proxy-accelerator mode. What I am
wondering is, what effect if any does the wmem_max
I have the following Apache::Registry script, which posts to itself. At the
top, I read in the posted values using CGI. If I receive one of them I die
to demonstrate my little bug. This causes a SERVER_ERROR to be returned to
apache, which then attempts to perform an internal redirect to a
