On Thu, 10 Nov 2011 02:05:44 +0100
Bostjan Skufca wrote:
> Seconded:)
>
> b.
Dear list,
To be confirmed I have installed debian squeeze on a new server having 8GB RAM
and with i5 processors. Then installed apache2, php5, mysql etc.
Have not done any tweak on any configuration and surpris
On November 10, 2011 15:38 , Nick Tkach wrote:
Second, we've seen that at least sometimes that seems to generate a
big spike in CPU usage "all of a sudden" once it goes live.
What seems to generate a big spike in CPU usage? When what goes live?
When the Apache HTTPD process gets started with
On Thu, Nov 10, 2011 at 2:23 PM, Mark Montague wrote:
> On November 10, 2011 14:41 , Nick Tkach wrote:
>>
>> Been Googling all over
>> trying to find details on any consequences/side-effects of using
>> mod_rewrite to redirect secure urls to other secure urls on the same
>> site. Something like
On November 10, 2011 14:41 , Nick Tkach wrote:
Been Googling all over
trying to find details on any consequences/side-effects of using
mod_rewrite to redirect secure urls to other secure urls on the same
site. Something like
RewriteRule ^https://mycom.com/specialsale
https://mycom.com/content/
Stupid system messed up that formatting, sorry. There's a space in
there between the "specialsale" and https:.
Another "wrinkle", would it make any difference if it was a
RedirectMatch as opposed to a RewriteRule?
On Thu, Nov 10, 2011 at 1:41 PM, Nick Tkach wrote:
> I've been looking at a part
I've been looking at a particular problem and it's one of those ones
that's just really hard to describe in unique terms for a search
(maybe no one else has hit it before :). Been Googling all over
trying to find details on any consequences/side-effects of using
mod_rewrite to redirect secure urls
