-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu 2007-05-03 14:36:39 -0400, Rainer Sokoll wrote:
> On Thu, May 03, 2007 at 10:49:21AM -0700, Don Russell wrote:
>> Rainer Sokoll wrote:
>
>> > RedirectMatch permanent ^/(.*) https://webmail.example.com/$1
>
>> Though that may work in many case
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu 2007-05-03 12:23:17 -0400, Bob wrote:
> The squirrelmail functionality is fine, just very very very
> slow. Any thoughts? I'm stumped.
This sounds like it could potentially be a DNS timeout. Is
squirrelmail trying to look up DNS information,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue 2007-05-01 13:07:56 -0400, M. Fioretti wrote:
> must this be done at every boot, or is this for playing with modules
> without restarting the whole server? Can't modules be turned off for
> good in the configuration file?
a2enmod and a2dismod
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue 2007-05-01 02:50:49 -0400, M. Fioretti wrote:
> Am I right? If yes, what are the best tips, tricks and configuration
> options (for apache and php) to make such a system as secure as
> possible and as light on the cpu as possible?
As a debian
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed 2007-04-25 21:00:54 -0400, Paul Lesniewski wrote:
> If there are three hits in the web log as you've shown, I think
> there is not much chance it'd be a SM problem. The request *did*
> appear to actually come three times. Unless there were so
