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.

Description of problem:
sblim-sfcb returns HTTP 501 Not Implemented over HTTPS

Version-Release number of selected component (if applicable):
sblim-sfcb-1.3.11-2.el6

How reproducible:
100%

Steps to Reproduce:
1. Configure sblim-sfcb for https
2. wbemcli ein -noverify https://user:pass@host:5989/root/virt:KVM_VirtualSystemManagementService

Actual results:
* wbemcli: Http Exception: Couldn't connect to server

Expected results:
sblim-sfcb is reachable without errors over HTTPS

Additional info:
It works normally if HTTPS is not used.

It appears to be the same cause as bz#968397

Sorry for the late timing. I would have sworn I filed this when we discovered it affected 6.6 three weeks ago, but I can't find it in bugzilla...