RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

+++ 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.

*** Bug 1302050 has been marked as a duplicate of this bug. ***

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