+++ This bug was initially created as a clone of Bug #1289096 +++
Description of problem:
Aged and/or broken TLS clients (notably java clients) behave unpredictably when responding with a SNI TLS warning and they assume it is an error. In order to work around these older and broken clients, RFC 6066 now recommends *not* sending a warning.
Version-Release number of selected component (if applicable):
httpd-2.4.6-40.el7.x86_64
How reproducible:
With the right broken clients, very.
Steps to Reproduce:
Do not have a self-contained reproducer I am afraid, but https://bz.apache.org/bugzilla/show_bug.cgi?id=56241 should show in detail what the problem is.
Actual results:
Clients suffer connection problems.
Expected results:
Clients does not suffer connection problems.
Additional info:
Have already discussed this with Joe Orton on IRC a couple weeks back.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHEA-2016-2534.html