With TLS 1.0 disabled this is causing some unneeded troubleshooting for some clients (clients being internal applications of various kinds, mostly case handling applications). By unneeded I mean that off course a warning has been issued about this, but not all system responsible has either read it or fully understood the consequence for their application. So if we could have configured a custom error message/page for clients expecting TLS 1.0 to be supported that would have been great.
Problem is - server returns a generic http 500, and we would like the error message to apply only for the TLS error. Is this in anyway possible for Apache to distinguish between a generic http 500 and a http 500 caused by TLS 1.0 not being supported?