Inline...
On 27 May 2011 20:52, Rob Morin wrote:
> We use a CDN for our images and other static files like CSS and so on…
>
>
>
> Like I mentioned keepalive is off as the Hosting company said we cannot use
> it in conjunction with keepalived on our haproxy setup, I guess I can test
> it on one m
We use a CDN for our images and other static files like CSS and so on.
Like I mentioned keepalive is off as the Hosting company said we cannot use
it in conjunction with keepalived on our haproxy setup, I guess I can test
it on one machine and see if anything goes awry..
I have not consider
Hi,
to replace the pattern 'https://www.abc.com' in this html code snippet
https://www.xyz.com/_layouts/AddGallery.xap?rev=hR
HsosXQNixIDlr8ntVz3Q%3D%3D">
I tried to apply the following rule
ProxyHTMLLinks param value
but it didn't apply.
Any ideas how to get this fixed? In cas
Hi Rob,
couple of thoughts below, please inform me if I make wrong deductions
somewhere, tnx.
1. Your static content is served from elsewhere, you are only talking about
application servers
2. Your average response time is 200ms, and given 4cores per server and
excluding delays you are currently
Hello,
Thank you for your replies. What i'm getting is the error 500 internal
server error when I place the .htaccess file. I'm not seeing anything
in the access log file except the reference to the 500 error. Running
a php cli on the php file does not return any errors syntax or
otherwise. I proba
Hi Martin,
the reverse proxy (gateway) in my case would be "apache1" me thinks. "apache2"
definitely does not use mod_proxy/ProxyPass. It is just loadbalancing two
tomcat
instances using "mod_jk".
My problem is (maybe I was not clear) that "apache2" does see the
X-Forwarded-For, X-Forwarded-
Hi,
sorry for the crosspost, but I am not sure where to ask. I am trying to
understand a weird problem accessing HTTP request headers from a jsf page.
The setup is as follows:
apache1 -> apache2 -> mod_jk -> tomcat
Apache1 is accessible from the Internet and forwards requests to my applicati
Thanks for all your help... first off I increased MaxRequestsPerChild from
1500 to 1 on one webserver, just as a test to make sure all is good
As for KeepAlive, we were told we cannot use it due to we are also using
keepalived on our haproxy load balancer, is this true?? As we have a bunch
> We also use New Relic and new PHP performance tuning tool, its very cool...
Oh, and remember to remove/comment out any PHP modules you aren't using. Every
PHP module you load (like the GD image module which
is loaded by default that people don't often use) is loaded up into the Apache
server
> Either the documentation at link below needs updating or
> there's a bug in Apache 2.2.17.
Or there's a user error. :-)
I tested once more before submitting bug report and now it's working, just as
documented. No changes on our side. I think our
servers can smell it when I'm posting here
> Does anyone have this working?
Yes. But, as noted under separate cover, it does not return a 404 status code
in 2.2.17 even when a local URL-path is used like in
the below. The lack of the 404 response will get you dinged by your favorite
search engine as the Apache documentation mentions.
E
#Increase this number. The zombies you're seeing
#is every time an Apache child process dies.
#The child will die @1500. We run at 2 and are having no problems.
MaxRequestsPerChild 1500
#We don't run as hot as you (we average 3 hits/sec and max at like 15
#in a 24 hour period) but here's
12 matches
Mail list logo
