Per RHQ-2009, similar to removing http/https from "rhq.communications.connector.transport", we should perhaps do the same for "rhq.agent.server.transport". [13:26] <cswiii> ping, re: http://jira.rhq-project.org/browse/RHQ-2009 -- out of curiosity, is it valid for 'rhq.agent.server.transport' to have http(s)? [13:29] <mazz> technically, we can use that, but people will probably never use it. (ssl)socket or (ssl)servlet are probalby the ones we really need [13:29] <mazz> we probably could remove those http(s).. I'm not sure if we really need those Repro steps: 1. Unpack agent plugin jar 2. navigate to rhq-plugin.xml 3. Search for rhq.communications.connector.transport 4. Observe results.
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-2253
Temporarily adding the keyword "SubBug" so we can be sure we have accounted for all the bugs. keyword: new = Tracking + FutureFeature + SubBug
making sure we're not missing any bugs in rhq_triage
as per: http://rhq-project.org/display/JOPR2/Communications+Configuration http://rhq-project.org/display/JOPR2/Securing+Communications the protocols that would only be used/supported is (ssl)servlet and (ssl)socket. commit af9ff8b removes http and https from the list of options
visual inspection of rhq-plugins.xml
Bulk closing of issues that were VERIFIED, had no target release and where the status changed more than a year ago.