You could add a load balancer/proxy that does SSL termination in front of
your web server (we use haproxy). If you are overloading your server, you
might just need to get another one.
- Y
Sent from a device with a very small keyboard and hyperactive autocorrect.
On Fri, Jan 25, 2019, 9:39 AM
Hi all,
I have one server and it is serving multiple websites:
eg.
www.example1.com
www.example2.com and such thousands of website and domains.
Each website has its own SSL certificate.
I made entry for each private key (SSLCertificateKeyFile), Certificate
(SSLCertificateFile), and CA Certificate
Thanks Stefan for explaining this. I hadn't managed to find anything when
searching for my problem. Based on the general expectations / docs (
https://httpd.apache.org/docs/2.4/mod/mod_reqtimeout.html*)*, that isn't
the behavior I'd have expected.
Do you know if there has been discussion about
mod_reqtimeout uses the setting of the "base" host, not necessarily the virtual
host selected by SSL.
The "base" host is usually the first one for the given port. So when you have
virtual host A, X, C in
that order in your config, try changing the setting for A.
-Stefan
PS. I find this not
I am runnning Apache HTTP2.4.34 (built from source on RHEL6.10).
RequestReadTimeout is being set at the Server level:
RequestReadTimeout header=5-10,MinRate=500 body=5-20,MinRate=500
I'm attempting to override RequestReadTimeout for a VirtualHost, I have
tried completely de-restricting