Hallo Alexaner,
Weil wir hier über 27 Länder-Sites einer Applikation sprechen, die nach und
nach umgeleitet werden müssen und der Overhead für die vHosts wäre enorm
mit mod_macro ist das sehr einfach zu realisieren ;)
Gruß
Mario
Hello Igor.
Thank you very much for your tip. Unfortunately the behavior is the same with
ProxyPassReverse statement. Do you have another recommendation?
Jarda
__
Od: Igor Cicimov icici...@gmail.com
Komu: users@httpd.apache.org
Hi,
I was talking about the binary files for Windows published in Apahce.Org
website. You can check the files in the link below. I have seen the 2.2.23
binary installation files fow Windows in this page including the OpenSSL-0.9.8t
as I have stated in previous e-mail. It is interesting that I
Hello.
I found the solution - problem was in stickysession=jsessionid|JSESSIONID. When
I switch value to stickysession=JSESSIONID|jsessionid the session affinity is
OK.
Jarda
__
Od: Jaroslav Fikker fik...@atlas.cz
Komu:
On Thu, Sep 27, 2012 at 4:05 AM, Görkem Durğüt gdur...@bkm.com.tr wrote:
Hi,
I was talking about the binary files for Windows published in Apahce.Org
website. You can check the files in the link below. I have seen the 2.2.23
binary installation files fow Windows in this page including the
Hello,
Over the years, I've experimented with a number of mechanisms by which
to force SSL connections to a website, while at the same time:
a.) Preventing the double-login problem.
b.) Eliminating entirely the potential for users to log-in over a
plain-text connection.
c.) Redirecting
We use mod_rewrite (non-relevant config removed):
VirtualHost *:80
Directory /var/www/admin
RewriteEngine On
RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}
/Directory
/VirtualHost
VirtualHost _default_:443
AddExternalAuth pwauth /usr/sbin/pwauth
On 9/27/2012 11:06 AM, Ben Johnson wrote:
Hello,
Over the years, I've experimented with a number of mechanisms by which
to force SSL connections to a website, while at the same time:
a.) Preventing the double-login problem.
b.) Eliminating entirely the potential for users to log-in
On 9/27/2012 11:55 AM, Yehuda Katz wrote:
We use mod_rewrite (non-relevant config removed):
VirtualHost *:80
Directory /var/www/admin
RewriteEngine On
RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}
/Directory
/VirtualHost
VirtualHost _default_:443
Hey folks o/~
One of my customers is running httpd/mod_disk_cache 2.2.16
with apr 1.2.x and experiencing the infamous
(103)Software caused connection abort: cache: error returned while trying to
return disk cached data
In one of my setups I'm running 2.2.14 with apr 1.3.9 and I'm
still
You can raise max client limit as bellow
MaxClients 250
But if there is any issue with the application/website you are running on
the Apache then it will reach to 250 also.
Do you have that many requests? 150 concurrent requests are meant for high
traffic site.
You need to analyze the problem
Hi..
Yes its a relay high traffic site, currently i just reduce some time out
values such as fallows .., make apache to kill child processors more
quickly. hopefully it makes some improvements
Timeout 700
KeepAliveTimeout 10
Thank You
john
On 28 September 2012 08:32, linuxsupport
You should keep the KeepAliveTimeout to 5, as 5 seconds are enough
Also, you could think of serving static contents from a threaded mpm
(worker in Apache) or use Nginx in front of Apache that should solve your
problem
On Fri, Sep 28, 2012 at 10:35 AM, val john valjohn1...@gmail.com wrote:
Hi..
13 matches
Mail list logo