Thanks for reporting the issue.
I believe that the links in that page are generated from the <url> value that is in the pom.xml of the jar file or war file that is used by Jenkins. Fixing the link in that page will need a fix to the value of the <url> tag in the matching component, then a new release of that component and the inclusion of that new release in Jenkins.
The first case seems feasible to fix by a change to add the <url> entry into war/pom.xml. I'm not clear on the side effects of adding that tag, but it seems reasonable at first glance.
Other cases may be more complicated to solve. In some cases (like Google Guice), it may be infeasible to solve until Jenkins is no longer dependent on an old version of Guice. See the discussions of a possible Guava upgrade to get some understanding of the dependency on the old version of Guice.
The HttpCommons Client Library appears to be trying to use a jenkins.io redirect to point the user to the correct repository for Apache HTTP Commons. You can read about jenkins.io redirects in the jenkins.io CONTRIBUTING doc.