https://bz.apache.org/bugzilla/show_bug.cgi?id=57360
--- Comment #6 from Joe Orton ---
FWIW I agree it's a bug this isn't caught by "httpd -t", but it would
definitely not be acceptable to silently "disable" some vhosts because the
certs were badly configured.
Looks like it might require some
https://bz.apache.org/bugzilla/show_bug.cgi?id=57360
Andrew G. Watters changed:
What|Removed |Added
CC||and...@andrewwatters.com
--
You
https://bz.apache.org/bugzilla/show_bug.cgi?id=57360
--- Comment #5 from Andrew G. Watters ---
This is still a bug as of 2022. I was panicking because I manage several
websites, all of which are under one certificate and were down for 45 minutes
while I troubleshooted. It would be really
https://bz.apache.org/bugzilla/show_bug.cgi?id=57360
Jaak Ristioja changed:
What|Removed |Added
CC||jaak+bz.apache.org@ristioja
https://bz.apache.org/bugzilla/show_bug.cgi?id=57360
Andreas Schnederle-Wagner changed:
What|Removed |Added
CC||schnede...@futureweb.at
https://bz.apache.org/bugzilla/show_bug.cgi?id=57360
--- Comment #4 from Andreas Schnederle-Wagner ---
This really odd behaviour just brought down one of our CMS Servers resulting in
~1.000 Websites being down for ~30 Minutes ...
We rely on automated "configtest" before doing "reload" - it
https://bz.apache.org/bugzilla/show_bug.cgi?id=57360
James Boyle changed:
What|Removed |Added
CC||un...@freeshell.org
https://bz.apache.org/bugzilla/show_bug.cgi?id=57360
--- Comment #2 from Michael Herold ---
I only proposed 1. and 2. since I thought 3. might be complicated. However, all
the tools required to do the necessary checks at configtest are in place.
Currently, the certificate/key