When I have had these issues in the past it is because Apache tends to limit
things to within server accessible locations, which for security is not the
whole hard disk. The strategies I have taken to solve these is create explicit
aliases in the httpd conf file, or sometimes easier, use
If you are looking to do this for cosmetic reasons, I do this be simply using
frame sets and doing redirects in the child frame. The URL displayed in the
location bar will always be constant for the parent frame. I don't think there
is any way to do this at the core level or it would be a
It seems to be just an attempt to do what is already done in
Apache2::AuthCookie (CPAN), which encapsulates a server side authentication.
-Original Message-
From: MK [mailto:m...@cognitivedissonance.ca]
Sent: Monday, July 11, 2011 3:37 PM
To: modperl@perl.apache.org
Subject: Re:
Database
Flatfile on disk (look up Storable module on how to save/load binary
representation of PERL structures), works well if you want to have an instant
structure, but flatfiles need location on the server.
I use both regularly
From: Jerry Pereira [mailto:online.je...@gmail.com]
Sent:
Hello,
I am attempting to get a clean up-to-date install Apache with static
linked mod_perl (using current stable releases for Apache (2.2.17) and
mod_perl (2.0.5) from .tar.gz files download from respective
repositories) but am at a frustrating dead end. I am looking for any
suggestions as
...@redhotpenguin.com]
Sent: Monday, April 18, 2011 12:33 PM
To: Szekeres, Edward
Cc: modperl@perl.apache.org
Subject: Re: Installation help [mod_perl 2.0.5/apache 2.2.17/perl-5.12.3]
On Mon, Apr 18, 2011 at 8:30 AM, Szekeres, Edward
edward.szeke...@perkinelmer.com wrote:
Hello,
I am attempting
Message-
From: Fred Moyer [mailto:f...@redhotpenguin.com]
Sent: Monday, April 18, 2011 2:44 PM
To: Szekeres, Edward
Cc: modperl@perl.apache.org
Subject: Re: Installation help [mod_perl 2.0.5/apache
2.2.17/perl-5.12.3]
On Mon, Apr 18, 2011 at 9:46 AM, Szekeres, Edward
edward.szeke
Moving an installation from Apache 1.3 to Apache 2.0.
I am trying to move an existing installation of a PERL code base (of
which I am not the original author) to Apache 2.0 to help address some
security concerns. For the most part I have found Apache2 equivalents
for most of the modules but