[users@httpd] mod_md: is a restart always require for auto updates?

I'm running Apache 2.4.43 and just added my first managed virtual host with mod_md and all worked fine. Now I want to move all my other virtual host to the same process but I have a few questions first: 1. For an auto renewal for the current managed domain, will I have to manually restart each tim

[users@httpd] Default 403 response when no matching vhost

Figure I would ask this here for the most graceful answer before making up my own. When running Apache for many vhosts (websites or acting as a reverse proxy), is there a way to make the default site (no matching vhost) return a 403 or 400 bad request similar to how Akamai does when no matching vh

[users@httpd] mod_proxyhealthcheck

Good afternoon everyone, I have a quick question. I am implementing mod_proxyhealthcheck my proxy ajp config has several load balancers pointing towards different apps on backend servers how do I setup mod_proxyhc to look at each lb uri individually using the same settings for failure and recovery

Re: [users@httpd] Default 403 response when no matching vhost

On Mon, Jul 13, 2020 at 1:02 PM Danny Mallory wrote: > > Figure I would ask this here for the most graceful answer before making up my > own. When running Apache for many vhosts (websites or acting as a reverse > proxy), is there a way to make the default site (no matching vhost) return a > 40

[users@httpd] TLS Client Hello not responded by mod_ssl

Dear Apache enthusiasts ... My application is a very simple https-only apache (2.4.43) server with mod_ssl (openssl 1.1.1g) in Linux (crux distribution 3.5). Using log levels up to trace8, I am unable to get anything useful past [...] [ssl:info] [...] [...] AH01964: Connection to child 64 est