Looks like you went the wrong direction with the rewrite. The ! is not.
You have not www.consumer-sc.ca.gov, then redirect.
RewriteCond %{HTTP_HOST} !^www\.consumer-sc\.ca\.gov$ [NC]
Should be
RewriteCond %{HTTP_HOST} ^www\.consumer-sc\.ca\.gov$ [NC]
Or even (which doesn't force the
The issue is that you are redirecting / to /a/
You can accomplish what you need with mod_rewrite, though I am not sure the
processing order for redirects done with Redirect and those done with
mod_rewrite so this might involve changing the Redirect permanent directives
to mod_rewrite redirect
[mailto:[EMAIL PROTECTED]
Sent: Friday, September 12, 2008 10:29 AM
To: users@httpd.apache.org
Subject: Re: [EMAIL PROTECTED] redirects conundrum
Ben Spencer wrote:
The issue is that you are redirecting / to /a/
You can accomplish what you need with mod_rewrite, though I am not
sure
How active are the sites? How complicated is the proxy configuration? Are
the Proxies an SSL termination point?
Server uptime: 50 days 3 hours 56 minutes 39 seconds
Total accesses: 36316506 - Total Traffic: 1544.5 GB
CPU Usage: u468.16 s2336.35 cu0 cs0 - .0647% CPU load
8.38 requests/sec - 373.7
Ther is no SSL involve what so ever.
The sites are very active (it is a share hosting environment and this
is
the reason why I wanna try the proxy) and beside that we plan to
expand.
We have between 50~300 reqs/sec (depend on time of the day) with around
10~20 kb/reqs and this is not the
Dedicated device = ??
What type of applications are running on server 1 server 2? Sticky
sessions being used? Explain a little more of your configuration.
You should also be able to get a feeling for the distribution of the
requests by using balancer-manager
benji
Benji Spencer
System
Thank you for the information and links.
You should put common directives into a separate file and Include[1]
them,
to avoid repetition.
Does this work within a virtualhost block?
Example:
VirtualHost *:80
ServerName: blah.com
# include standard RewriteRules
Include
Probing to see if people have a good way/tools which people use to manage
their apache configuration file(s). we have roughly 50 virtual hosts which
are divided into roughly four major applications with each application
having some common configuration directives. While copy/paste works, it is
We are looking to purchase a bulk number of SSL certificates for a variety
of sites. As we were discussing this with our current SSL certificate
provider, we ran into something which sounds a little odd, and wonder if
others have run into this with their bulk SSL certificate purchases.
When the
That is a PHP session (tmp) file.
http://us.php.net/manual/en/ref.session.php
benji
---
Benji Spencer
System Administrator
Ph: 312-329-2288
-Original Message-
From: Marc Fromm [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 13, 2008 1:07 PM
To: users@httpd.apache.org
Subject:
Configuration: 2 servers which use two different cookies to help maintain
sessions. The cookies are set domain wide so each server can actually update
the others cookies.
When a request is sent to either server, I want to be able to update the
others cookies (session timeout time) with
This is a simple task, except that the value of the cookie actually has
a : in it which confuses mod_rewrite and the parameters since the
parameter separator is a :.
You just need to escape the colon as %3A (percentage-three-uppercase A).
HmmmThanks. How to do that in the apache
: [EMAIL PROTECTED] Apache able to cache entire HTML page?
On 04/09/07, Ben Spencer [EMAIL PROTECTED] wrote:
Question:
Can apache cache everything for an undefined amount of time
(days/months/years) without concern of the backend server's headers?
With
some playing, we got this to work
Background:
We have a CMS system which generally houses rarely-updated content (the
content providers are outside of our group and of course want to be able to
push updates out whenever they want). Saddly, the CMS system really can't
keep up with the traffic we receive without many backend
We are successfully using proxy_load_balancer to load balance requests to
backend IIS servers. We noticed that if a site on one of the IIS servers
is turned off, Apache still considers it a member and will send requests to
it. IIS responds with a 503 (I think -- no site configured for this name or
15 matches
Mail list logo
