While addressing the 'sslget' issues documented in:
it was suggested that 'sslget' could be improved to handle issues associated with connection errors in a more robust manner.
For example:
Right now the code rifles through the NSPR returned list of candidate IP addresses for a given connection. It tries the first available one being IPv4 or IPv6 addresses. If the first available candidate address fails, the program gives up.
Alee would like the tool to be improved such that it will intelligently progress through the list of candidate addresses one at a time in the following fashion:
Filter out link local addresses which we have trouble connecting to. (The code does this already)
Come up with a criteria by which to attempt subsequent addresses in the candidate list, knowing when to give up entirely. The idea is to be able to select a live address amongst the list without spending too much time churning through a list of addresses sure to fail. This will involve the intelligent evaluation of the return codes presented by failed connection attempts.
Metadata Update from @mharmsen: - Issue set to the milestone: UNTRIAGED
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/1166
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Metadata Update from @dmoluguw: - Issue close_status updated to: migrated - Issue status updated to: Closed (was: Open)