I am trying to enable the apache module mod_speling on apache 1.3.27
I enable it find but it doesn't seem to support the
CheckCaseOnly
Apache directive.
Dunno about a list, but your problem is that directive was only added in
Apache 2.2
The docs for apache 1.3 are here:
http://httpd.apach
Dear listmember,
as I am new to the list, so please let me disclaim, that I already
searched the archives, read at perl.apache.org and other documentation,
I am insane and sensible. :)
I am trying to modify incoming http cookie on the fly. The setup is like
user->webserver->bea connector->be
On Friday 01 June 2007 12:15, Daniel Eckstein wrote:
> I am trying to modify incoming http cookie on the fly. The setup is like
>
> user->webserver->bea connector->bea appserver
You can certainly do that using a connection input filter. But I'd say that is
much too complicated.
Apache processes
i'm facing the problem reported in
http://issues.apache.org/bugzilla/show_bug.cgi?id=30901
when using mod_perl 2 on sparc solaris 10 with apache 2.0.58
as this bug is said to be resolved (but still there) does someone know
about it (workaround ? way to launch the mod_perl test suite)
?
thanks i
On 6/1/07, Daniel Eckstein <[EMAIL PROTECTED]> wrote:
Primary goal is to modify incoming cookies before they reach the
connector module for bea. It would be even possible to put a additional
reverse proxy before the webserver to accomplish this. Like
user->reverse proxy -> webserver-> bea conne
Okay, am being a bit lazy but I though I'd ask here and continue reading the
docs while waiting for replies.
We've finally ported mod_perl 1.99 to a lovely new mod_perl 2.0.n but some
things don't work. Namely PerlSetENV
This works under mod_perl but not CGI. Is there something else I should be
PerlSetENV will only make your environment variables available to perl
handlers. If you want them also available to CGI, you have to set them
twice, once with PerlSetENV and again with Apache's regular SetENV. If
there's a better way to do it, I'm sure someone on the list will speak up :)
Hi
When using a MySQL database with modperl 2. I can find lots of docs on
using DBI, but not much on what is the best practice...
I am currently connecting, using the db and exiting on each request, and
relying on Apache::DBI to cache the connection. E.g.
use Apache::DBI;
sub handler {
#
On Jun 1, 2007, at 7:47 PM, Matt Williamson wrote:
Hi
When using a MySQL database with modperl 2. I can find lots of docs on
using DBI, but not much on what is the best practice...
I am currently connecting, using the db and exiting on each
request, and
relying on Apache::DBI to cache the
On 6/1/07, Jonathan Vanasco <[EMAIL PROTECTED]> wrote:
> When using a MySQL database with modperl 2. I can find lots of docs on
> using DBI, but not much on what is the best practice...
A lot of it is covered here:
http://modperlbook.org/html/ch20_02.html
you also might want to add a cleanup
10 matches
Mail list logo