Steven Christenson there are many different ways that a tables to div issue could prevent saving a Jenkins job configuration or global configuration.
Getting help with the specific issue you're seeing requires specific steps to duplicate the problem and a specific, detailed list of the exact plugins and versions installed in Jenkins. There is a groovy script that will output the plugin names and versions in a format that others can use to help diagnose the issue.
You mentioned that you believe it is somehow related to apache-httpcomponents-client-4-api. I've not seen any cases where that API plugin was related in any way to a failure to save a Jenkins configuration form. I realize that sriram says that the issue was resolved by an upgrade to apache http components plugin yet the most recent release of that plugin was over 5 months ago and the changelogs for the releases from the last two years do not mention anything that would suggest to me that it would alter the saving of HTML forms. I suspect that the "upgrade" that fixed sriram was also an upgrade of some other plugin that needed a fix for tables to divs. Can you describe further why you believe that apache http components it is related to the problem you're seeing?
It is usually best to provide a new bug report for this type of issue, rather than commenting on an existing bug report. This bug report is specific to the artifactory plugin. Since you say that you do not have the artifactory plugin, this bug does not describe your case. The new bug report needs to include the precise list of plugins that are installed, the version numbers of those plugins, and the detailed steps required for another persons to see the problem that you're seeing.
You suggested that "up for adoption" means a plugin is "basically unsupported". That's not really the case, especially in the case of an API plugin like the Apache HTTP components API plugin. A plugin that is "up for adoption" has been noted by the maintainer that they would like help from others to maintain the plugin. The apache http components plugin 4.5.13 matches the Apache HTTP components API 4.5.13 release. That is the most recent release of the Apache HTTP 4.5 library. The Apache HTTP Components status page describes the 4.5 series as:
HttpClient 4.5.x branch is considered stable and production ready. While being actively maintained and supported, the 4.x release series will be receiving fixes for major defects and security issues only.
Yes, we'd love to have more maintainers, but since that API plugin is synchronized with its matching upstream release, I don't see that as a cause for concern.
You mentioned that you're running 2.277.4.3. That's a CloudBees version number. That usually means you have a support contract with CloudBees and can request help from the CloudBees support team.